administrator: Configures the default domain for context-level administrative users.
subscriber: Configures the default domain for subscribers.
domain_name must be an alphanumeric string of 1 through 79 characters.
Important: This command is only available in 8.3 and later releases.aaa domain-matching imsi-prefix prefix-length prefix_length
prefix_length must be an integer from 1 through 15.
Important: For this command to take affect, after entering the command the configuration must be saved and reloaded.|
•
|
Only one (1) NAS IP address can be defined per context with the radius attribute command.
|
|
•
|
administrator: Configures the last resort domain for context-level administrative.
subscriber: Configures the last resort domain for the subscribers.
Specifies the context which is to be set as the last resort. context_name must be an alphanumeric string of 1 to 79 characters.
The following command removes the previously configured domain called sampleAdministratorDomain:
domain: indicates the left side of the string from the separator character is a domain name and the right side is the user name.
username: indicates the left side of the string from the separator character is a user name and the right side is the domain name.
Important: The user name string is always searched from right to left for the first occurrence of the separator character.no active-charging service acs_service_name
acs_service_name must be the name of an Active Charging Service, and must be an alphanumeric string of 1 through 15 characters.
Use this command after enabling ACS using the require active-charging command. This command allows administrative users to configure the ACS functionality.
Enables or disables alarming options for the SPIO card internal alarms and the central-office external alarms. To verify the state of the alarms, refer to the show alarm command.
audible: indicates the internal audible alarm on the SPIO cards are to be enabled.
central-office: indicates the central office alarms are to be enabled.
[ no ] apn-profile apn_profile_name
Use this command to create an instance of an APN profile and to enter the APN profile configuration mode. An APN profile is a template which groups a set of APN-specific commands that may be applicable to one or more APNs. See the APN Profile Configuration Mode Commands chapter for information regarding the definition of the rules contained within the profile and the use of the profile.
Important: An APN profile is a key element of the Operator Policy feature and is only valid when associated with at least one operator policy.To see what APN profiles have already been created, return to the Exec mode and enter the show apn-profile all command.
[ no ] apn-remap-table apn_remap_table_name
Use this command to create an instance of an APN remap table and to enter the APN remap table configuration mode. An APN remap table includes entries that define how an incoming APN, or the lack on one, will be handled. See the APN Remap Table Configuration Mode Commands chapter for information regarding the definition of the entries contained within the table and the use of the table.
Important: An APN remap table is a key element of the Operator Policy feature and is only valid when associated with at least one operator policy.To see what APN remap tables have already been created, return to the Exec mode and enter the show apn-remap-table all command.
Use this command to configure a system-wide ARP refresh interval. Once a neighbor is found, the entry is considered valid for at least a random value between the time/2 and the time*1.5.
Important: To change the behavior for the current CLI session only, use the autoconfirm command in the Exec Mode.By default autoconfirm is enabled.
Refer to the Lawful Intercept Configuration Guide for a description of this parameter.
Important: This banner is displayed only for serial port and telnet log ins. It is not supported in ssh and, therefore, will not be displayed before ssh log ins.Specifies the banner or message to be displayed at session initialization. string may be an alphanumeric string of 0 through 2048 characters. The string must be enclosed in double quotation marks if the banner or message is to include spaces.
boot delay time
Important: The settings for this command are stored immediately in the boot.sys file. No changes are made to the system configuration file.The following sets the boot delay to 10 seconds:
boot interface { spio-eth1 | spio-eth2 } [ medium { auto | speed medium_speed duplex medium_duplex } [ media medium_media ] ]
spio-eth1 | spio-eth2
Specifies the network interface to be configured where spio-eth1 is the primary interface on the SPIO (slot 24 interface 1 or slot 25 interface 1) and spio-eth2 is the secondary interface on the SPIO (slot 24 interface 2 or slot 25 interface 2). The interfaces refer to either the RJ-45 interfaces for speeds of 10, 100, or 1000 megabit per second (Mbps), or the SFP interface for the optical gigabit (1000 Mbps) interface.
auto: configures the interface to auto-negotiate the interface speed. and duplex.
speed medium_speed duplex medium_duplex: specifies the speed to use at all times where medium_speed must be one of:
|
•
|
|
•
|
|
•
|
The keyword duplex is used to set the communication mode of the interface where medium_duplex must be one of:
|
•
|
|
•
|
media medium_media
Optionally sets the physical interface where medium_media must be either rj45 or sfp.
Important: The settings for this command are stored immediately in the boot.sys file. No changes are made to the system configuration file.boot nameserver ip_address
Important: The settings for this command are stored immediately in the boot.sys file. No changes are made to the system configuration file.no boot system priority number
priority number
Important: When performing a software upgrade it is important that the new file group have the highest priority (lowest value) configured.
Important: To ensure that higher priority numbers remain open, use an “N-1” priority numbering methodology, where “N” is the first priority in the current boot stack.image image_url
|
•
|
|
•
|
Important: Use of the SMC hard drive is not supported in this release.
Important: Do not use the following characters when entering a string for the field names below: “/” (forward slash), “:” (colon) or “@” (at sign). directory is the directory name.
filename is the actual file of interest.
host is the IP address or host name of the server.
port# is the logical port number that the communication protocol is to use.
Important: A file intended for use on an ASR 5000 uses the convention xxxxx.asr5000.bin, where xxxxx is the software build number.
Important: When using the TFTP, it is advisable to use a server that supports large blocks, per RFC 2348. This can be implemented by using the “block size option” to ensure that the TFTP service does not restrict the file size of the transfer to 32MB.config config_path
|
•
|
|
•
|
Important: Use of the SMC hard drive is not supported in this release.Where path is the directory structure to the file of interest, and filename is the name of the configuration file. This file typically has a .cfg extension.
Important: The configuration file must reside on the local filesystem, stored on one of its local devices (/flash, /pcmcia1, /hd-raid). Attempts to load the configuration file from an external network server will result in a failure to load that image and configuration file group, causing the system to load the image and configuration file group with the next highest priority in the boot stack.
Important: Configuration changes do not take effect until the system is reloaded.
Important: The settings for this command are stored immediately in the boot.sys file. No changes are made to the system configuration file.The following removes the current priority 1 boot entry from the boot.sys file.
[<context-name>]asr5000(config-bulkstats)#
The Bulk Statistics Configuration Code consists of commands for configuring bulk statistic properties, such as the period of collection. Bulk Statistics configuration mode commands are defined in the Bulk Statistics Configuration Mode Commands chapter.
Once bulk statistics receiver, schema, and collection properties are configured, this bulkstats command is used to enable or disable the collection of the data.
To collect a sample that will provide an average, for example, an average of CPU counters, the “historical” features must be enabled with the bulkstats historical collection command.
Since bulk statistics are collected at regular, user-defined intervals, the bulkstats force command in the Exec Mode can be used to manually initiate the collection of statistics at any time.
name name
Names the CA certificate. name must be an alphanumeric string of 1 through 128 characters.
data pemdata
CA certificate data in PEM format. pemdata must be an alphanumeric string of 1 through 4095 characters.
url url
URL of the file containing CA certificate in PEM. url must be an existing URL expressed in one of the following formats:
When read via a file, note that show configuration will not contain the URL reference, but will instead output the data via data pemdata, such that the configuration file is self-contained.
no ca-crl name name
Provides a name of the CA-CRL. name must be an alphanumeric string of 1 through 128 characters.
url url
Specifies the URL where the CA-CRL is to be fetched. url must be an existing URL expressed in one of the following formats:
The following command fetches a CA-CRL named list1.pem from a host.com/CRLs location and names the list CRL5:
card number
Specifies the number of the card for which the card configuration mode is to be entered. number must be an integer from 1 through 48.
Important: This command is not supported on all platforms.Specifies the slot of the card for the order of the standby cards. slot_num must be in the range from 1 through 16 excluding slots 8 and 9. slot_num may be repeated as many times as necessary to indicate the complete search order.
Important: This command replaces the pac-standby-priority command.
Important: This command is not supported on all platforms.[ no ] call-control-profile cc_profile_name
Use this command to create an instance of a call-control profile and to enter the call-control profile configuration mode. A call-control profile is a template which groups a set of call-handling instructions that may be applicable to one or more incoming calls. See the Call-Control Profile Configuration Mode Commands chapter for information regarding the definition of the rules contained within the profile and the use of the profile.
Important: A call-control profile is a key element of the Operator Policy feature and is only valid when associated with at least one operator policy.To see what call-control profiles have already been created, return to the Exec mode and enter the show call-control-profile all command.
Important: For changes to this command to take effect, save the configuration and reboot the system.
Important: In multi-CDRMOD mode, you should enable hard-disk usage.certificate name name pem { data pemdata | url url } private-key pem { [ encrypted ] data pemdata | url url }
no certificate name name
name name
Names the certificate. name must be from 1 to 128 alphanumeric characters.
data pemdata
Certificate/private key data in PEM format. pemdata must be an alphanumeric string of 1 through 4095 (certificate) or 1 through 8191 (private key) characters.
url url
URL of the file containing certificate/private key in PEM. url must be an existing URL expressed in one of the following formats:
When read via a file, show configuration will not contain the URL reference, but instead outputs the data via data pemdata, such that the configuration file is self-contained.
cli { access { monitor-protocol | monitor-subscriber | show-configuration } { administrator | operator } } | login-failure-delay number | max-sessions number | operator clear-subscriber-one-only | trap config-mode }
no cli { max-sessions | login-failure-delay number | operator clear-subscriber-one-only | trap config-mode }
default cli { access { monitor-protocol | monitor-subscriber | show-configuration } | max-sessions | login-failure-delay number | operator clear-subscriber-one-only | trap config-mode }
monitor-protocol: Selects privileges for the monitor protocol command.
monitor-subscriber: Selects privileges for the monitor subscriber command.
show-configuration: Selects privileges for the show-configurationcommand. However the default access level for this command is the user with operator privileges.
operator: Sets the privileges for the selected command to allow use by users with operator privileges.
administrator: Restricts use of the selected command to administrators only.
login-failure-delay number
max-sessions number
Sets the number of allowed simultaneous CLI sessions on the system. If this value is set to a number below the current number of open CLI sessions, the open sessions will continue until closed. number must be an integer from 2 through 100.
Caution: Use caution when setting this command. Limiting simultaneous CLI sessions prevents authorized users from accessing the system if the maximum number allowed has been reached. The system already limits CLI sessions based on available resources. Additional limitation could have adverse effects.The following command sets the command monitor protocol to administrator-only
Indicates the timezone specified by tz is to be considered the local time zone for local time display and conversion.
|
•
|
Congestion condition thresholds: Thresholds dictate the conditions for which congestion control is to be enabled and establish limits for defining the state of the system (congested or clear). These thresholds function in a similar fashion to the operation thresholds that can be configured for the system (as described in later in this chapter). The primary difference is that when these thresholds are reached, not only is an SNMP trap generated (starCongestion), but a service congestion policy is invoked as well.
|
|
•
|
Service congestion policies: Congestion policies are configurable for each service (PDSN, GGSN, or HA). These policies dictate how services respond should the system detect that a congestion condition threshold has been crossed.
|
Because congestion control functionality on the system is disabled by default, this command should be executed once congestion-control thresholds and policies have been configured. (Refer to the congestion-control policy and congestion-control threshold commands for more information.)
congestion-control overload-disconnect [ iterations-per-stage integer | percent percentage_value | threshold { license-utilization percentage_value | max-sessions-per-service-utilization percentage_value | tolerance number } ]
iterations-per-stage integer
Specifies the number of calls to be disconnected during the defined number of seconds. integer is a value from 2 through 8. The default value is 8.
percent percentage_value
Specifies the percentage of calls to be disconnected, in stages, during an overload situation. percentage_value is an integer from 1 through 100. The default value is 5.
license-utilization: Specifies the license-utilization percentage threshold for overload situations. If candidates are available, passive calls are disconnected when this threshold is exceeded. percentage_value is an integer from 1 through 100. The default value is 80.
max-sessions-per-service-utilization: Specifies a percentage of the maximum sessions per service. If candidates are available, passive calls are disconnected when this threshold is exceeded. percentage_value is an integer from 1 through 100. The default value is 80.
tolerance:Specifies the percentage of calls the system disconnects below the values set for the other two thresholds. In either case, a Clear Traps message is sent after the number of calls goes below the corresponding threshold value. number is an integer from 1 through 25. The default value is 10.
To verify the congestion-control configuration use show congestion-control configuration from the Exec mode.
To set overload-disconnect policies for individual subscribers., see overload-disconnect in Subscriber Configuration Mode Commands.
|
•
|
drop: Specifies that the system is to drop incoming packets containing new session requests.
|
|
•
|
none: Specifies that the system is take no action.
|
|
•
|
reject: Specifies that the system processes new session request messages and responds with a reject message.
|
For MME type of session/calls redirect action is not supported.
|
•
|
drop: Specifies that the system is to drop incoming packets containing new session requests.
|
|
•
|
none: Specifies that the system is take no action.
|
|
•
|
reject: Specifies that the system processes new session request messages and responds with a reject message.
|
|
•
|
drop: Specifies that the system is to drop incoming packets containing new session requests.
|
|
•
|
none: Specifies that the system is take no action.
|
|
•
|
reject: Specifies that the system processes new session request messages and responds with a reject message.
|
|
•
|
drop: Specifies that the system is to drop incoming packets containing new session requests. (PDSN, GGSN, ASN GW, LMA, MME, and ASN PC and HA only)
|
|
•
|
none: Specifies that the system is take no action. This is the default for PDIF-service.
|
|
•
|
redirect: Specifies that the system is to redirect new session requests to an alternate device. (PDSN and HA only)
|
Important: If this option is used, the IP address of the alternate device must be configured using the policy overload redirect command that is part of the service configuration. Note that this option can not be used in conjunction with GGSN and MME services.|
•
|
reject: Specifies that the system processes new session request messages and responds with a reject message. (For PDSN and HA, the reply code is 130, “insufficient resources”. For the GGSN, the reply code is 199, “no resources available”.)
|
Important: This set of keywords is supported only by the MME.permit-emergency-sessions: Specifies that only emergency sessions are allowed to access the MME during the overload period.
reject-new-sessions: Specifies that all new sessions destined for the MME will be rejected during the overload period.
reject-non-emergency-sessions: Specifies that all non-emergency sessions will be rejected during the overload period.
enodeb-percentage percentage: Configures the percentage of known eNodeBs that will receive the overload report. percentage must be an integer from 1 to 100.
congestion-control threshold { license-utilization percent | max-sessions-per-service-utilization percent | message-queue-utilization percent | message-queue-wait-time time | port-rx-utilization percent | port-specific { slot/port | all } [ tx-utilization percent ] [ rx-utilization percent ] | port-tx-utilization percent | service-control-cpu-utilization percent | system-cpu-utilization percent | system-memory-utilization percent | tolerance percent }
no congestion-control threshold port-specific { slot/port | all } [ rx-utilization percent ] [ tx-utilization percent ]
no congestion-control threshold { message-queue-utilization | message-queue-wait-time | port-rx-utilization percent | port-tx-utilization percent | service-control-cpu-utilization | system-cpu-utilization | system-memory-utilization }
slot/port: Specifies the port for which port specific threshold monitoring is being configured. The slot and port must refer to an installed card and port.
all: Set port specific threshold monitoring for all ports on all cards.
license-utilization percent
percent can be configured to any integer value from 0 to 100.
The percent utilization of the maximum sessions allowed per service as measured in real-time. This threshold is based on the maximum number of sessions or PDP contexts configured for the a particular service. (Refer to the bind command for the PDSN, GGSN, SGSN, or HA services.)
percent can be an integer from 0 through 100.
message-queue-utilization percent
percent can be an integer from 0 through 100.
time is measured in seconds and can be an integer from 1 through 30.
Important: In the event that this threshold is crossed, an SNMP trap is not triggered. The service congestion policy invocation resulting from the crossing of this threshold is enforced only for the packet that triggered the action.[no] port-rx-utilization percent
percent can be an integer from 0 through 100.
slot/port: Specifies the port for which port-specific threshold monitoring is being configured. The slot and port must refer to an installed card and port.
all: Set port specific threshold monitoring for all ports on all cards.
rx-utilization percent: Default 80%. The average percent utilization of port resources for the specified port by received data as measured in 5 minute intervals. percent must an integer from 0 through 100.
tx-utilization percent: Default 80%. The average percent utilization of port resources for the specified port by transmitted data as measured in 5-minute intervals. percent must be an integer from 0 through 100.
[ no ] port-tx-utilization percent
percent can be an integer from 0 through 100.
service-control-cpu-utilization percent
percent can be an integer from 0 through 100.
system-cpu-utilization percent
percent can be an integer from 0 through 100.
This threshold setting can be disabled with no congestion-control threshold system-cpu-utilization command. In case later you want to enable the same threshold setting congestion-control threshold system-cpu-utilization command will enable the CPU utilization threshold to preconfigured level.
system-memory-utilization percent
percent can be an integer from 0 through 100.
tolerance percent
percent can be an integer from 0 through 100.
This setting will remain in configuration unless you specify another threshold value in place of 75. This threshold setting can be disabled with no congestion-control threshold system-cpu-utilization command but cannot be removed from configuration. Later if you want to enable the previously configured threshold value of 75 percent, you only need to enter the congestion-control threshold system-cpu-utilization command without specifying any threshold value. It will enable the CPU utilization threshold to preconfigured level of 75 percent.
For example, no congestion-control threshold system-cpu-utilization disables the configured threshold setting and congestion-control threshold system-cpu-utilization again enables the threshold setting of 75%.
content-filtering category database directory path directory_path
directory_path must be an alphanumeric string of 1 through 255 characters.
Merging of incremental database can be done as part of the database upgrade process preformed with upgrade content-filtering category database command in the Executive Mode.
The following command configures the /flash/cf_temp/DB as the base directory to download all full and incremental content-rating databases for content filtering application.
content-filtering category database max-versions num_archive
num_archive must be an integer from 1 through 3.
Use this command to set the number of full content-rating database to be maintained in the specified directory path with the base file name specified using the content-filtering database override file command. The specified directory path is the location specified using the content-filtering category database directory path command.
The following command configures the system to maintain 3 full content-rating databases for category-based content filtering application.
file_name must be an alphanumeric string of up to 10 characters with an extension of 3 characters after a period (.) as extension.
Use this command to configure the category-rating database file name to determine the newest version of full database. A process called “LOAD_DATABASE” invokes during the system startup or the database upgrade process by upgrade content-filtering category database command in Executive Mode. This process examines the header of each of the files in the database folder specified by content-filtering category directory path command in this mode.
The following command configures the system to examine the header of files that begins with CF_sta.DB only for content filtering application.
no context name
Important: When creating a new context, the context name specified must not conflict with the name of any existing context or domain names.
Important: A maximum of 64 contexts may be created.context sampleContext
no context sampleContext
Important: System crash information is generated and stored in the crash list even when the no keyword is specified. The information maintained in the crash lists is minimal crash information when the no keyword has been specified.filename-pattern pattern
The filename-pattern is a an alphanumeric string containing any or all of the following variables:
|
•
|
%hostname% - The system hostname.
|
|
•
|
%ip% - A SPIO IP address
|
|
•
|
%cpu% - CPU number
|
|
•
|
%card% - Card number
|
|
•
|
%time% - POSIX timestamp in hexadecimal notation
|
|
•
|
|
•
|
%% - A single % sign
|
url crash_url
Specifies the location to store crash files. crash_url may refer to a local or a remote file. crash_url must be entered using the following format:
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
Important: Use of the SMC hard drive is not supported in this release.
Important: Do not use the following characters when entering a string for the field names below: “/” (forward slash), “:” (colon) or “@” (at sign). directory is the directory name.
filename is the actual file of interest.
username is the user to be authenticated.
password is the password to use for authentication.
host is the IP address or host name of the server.
port# is the logical port number that the communication protocol is to use.
restrict mbyte
The restrict keyword is only applicable to local URLs.
no cs-network cs_instance
Caution: Removing the HNB-CS network instance is a disruptive operation and it will affect all UEs accessing MSC(s) configured in specific CS core network through the HNB-GW service.
Caution: If any HNB-CS Network instance is removed from system all parameters configured in that mode will be deleted and Iu-CS/Iu-Flex interface will be disabled.Specifies the name of the Circuit Switched Core Networks instance which needs to be associated with the HNB Radio Network PLMN via the HNB RN-PLMN Configuration mode. If cs_instance does not refer to an existing HNB-PS network instance, the new HNB-CS network instance is created.
cs_instance must be an alphanumeric string of 1 through 63 characters.
Caution: This is a critical configuration. The HNBs cannot access MSC(s) in CS core network without this configuration. Any change to this configuration would lead to disruption in HNB access to CS core network.The various parameters available for configuration of an HNB-CS network instance are defined in the HNB-CS Network Configuration Mode Commands chapter.
The following command will remove HNB-CS network instance hnb-cs1 from the system without any warning to operator:
lawful-intercept - Restores the system default message of the day for SSH CLI sessions.
motd - Restores the system default message of the day banner.
pre-login - Restores the CLI log in banner to the system default.
interface | networkconfig - Restores the default boot interface and network configuration options. The keywords interface and networkconfig are used to restore the default option settings for the interface and network configuration options, respectively.
delay - Removes the boot delay setting (if any). The default for boot delay is “no boot delay”.
nameserver - Removes the nameserver IP address.
Restores the default value of this command to no cli max-sessions which removes the limit on the number of allowed simultaneous CLI sessions on the system.
display: sets the default level of detail to display for trace log information to the system default.
filter runtime: resets the filtering of logged information to log in real time.
This parameter has been replaced by the card-standby-priority keyword.
|
•
|
|
•
|
priority: All DSCP values are mapped to the best-effort priority queue but are not configured.
|
engine-id: restores the SNMP engine ID to the system default.
notif-threshold: restores the SNMP notification threshold to the system default.
facility sessmgr start: Restores the default session manager start policy.
resource cpu-memory-low: Resets the system so that when a CPU runs very low on memory (below 12MB) the most over limit task is killed.
|
•
|
10sec-cpu-utilization: CPU utilization using a 10 sec average.
|
|
•
|
aaa-acct-archive-size: AAA accounting archive queue threshold settings
|
|
•
|
aaa-acct-failure: AAA accounting failure threshold settings
|
|
•
|
aaa-acct-failure-rate: AAA accounting failure rate threshold settings
|
|
•
|
aaa-auth-failure: AAA authentication failure threshold settings
|
|
•
|
aaa-auth-failure-rate: AAA authentication failure rate threshold settings
|
|
•
|
aaa-retry-rate: AAA retry rate threshold settings
|
|
•
|
aaamgr-request-queue: AAA manager internal request queue threshold settings
|
|
•
|
call-reject-no-resource: Calls rejected due to no resources threshold settings
|
|
•
|
call-setup: Calls setup threshold settings
|
|
•
|
call-setup-failure: Call setup failure threshold settings
|
|
•
|
contfilt-block: Content Filtering Blocks threshold settings
|
|
•
|
contfilt-rating: Content Filtering Ratings threshold settings
|
|
•
|
cpu-available-memory: CPU available memory threshold settings
|
|
•
|
cpu-load: PSC/PSC2 CPU load using a 5 minute average measurement
|
|
•
|
cpu-memory-usage: Percentage of total CPU memory usage
|
|
•
|
cpu-session-throughput: CPU session throughput threshold settings
|
|
•
|
cpu-utilization: CPU utilization threshold settings
|
|
•
|
dcca-bad-answers: Diameter Bad Answers threshold settings
|
|
•
|
dcca-protocol-error: Diameter Protocol Error threshold settings
|
|
•
|
dcca-rating-failed: Diameter Rating Failed threshold settings
|
|
•
|
dcca-unknown-rating-group: Diameter Unknown Rating Group threshold settings
|
|
•
|
diameter: Diameter threshold settings
|
|
•
|
license: Session license threshold settings
|
|
•
|
model: Thresholding model settings
|
|
•
|
monitoring: Threshold monitoring configuration settings
|
|
•
|
packets-filtered-dropped: Filtered/dropped packet threshold settings
|
|
•
|
packets-forwarded-to-cpu: Forwarded packet threshold settings
|
|
•
|
pdif-current-sessions: Threshold monitoring for all current PDIF sessions.
|
|
•
|
pdif-current-active-sessions: Threshold monitoring for only the currently-active PDIF sessions.
|
|
•
|
per-service-ggsn-sessions: The number of GGSN sessions per GGSN service
|
|
•
|
per-service-gprs-sessions: The number of GPRS sessions per GPRS service
|
|
•
|
per-service-gprs-pdp-sessions: The number of PDP contexts per GPRS service
|
|
•
|
per-service-ha-sessions: The number of HA sessions per HA service
|
|
•
|
per-service-lns-sessions: The number of LNS sessions per LNS service
|
|
•
|
per-service-pdsn-sessions: The number of PDSN sessions per PDSN service
|
|
•
|
per-service-sgsn-sessions: The number of SGSN sessions per SGSN service
|
|
•
|
per-service-sgsn-pdp-sessions: The number of PDP contexts per SGSN service
|
|
•
|
poll: Threshold polling interval configuration settings
|
|
•
|
total: Total subscriber threshold settings
|
|
•
|
total-ggsn-sessions: Total GGSN sessions for all GGSN services in the system
|
|
•
|
total-gprs-sessions: Total GPRS sessions per for all GPRS services in the system
|
|
•
|
total-gprs-pdp-sessions: Total PDP contexts for all GPRS services in the system
|
|
•
|
total-ha-sessions: Total HA sessions for all HA services in the system
|
|
•
|
total-lns-sessions: Total LNS sessions for all LNS services in the system
|
|
•
|
total-pdsn-sessions: Total PDSN sessions for all PDSN services in the system
|
|
•
|
total-sgsn-sessions: Total SGSN sessions per for all SGSN services in the system
|
|
•
|
total-sgsn-pdp-sessions: Total PDP contexts for all SGSN services in the system
|
time: Resets the maximum time a session may exist during a software upgrade to the default of 120.
usage: Resets the minimum number of sessions before closing the sessions during a software upgrade to the system default of 100.
diameter-proxy ram-disk mb space_mb
space_mb must be an integer from 10 through 256.
The following command specifies that 100 MB of additional storage space be allocated to the Diamproxy task:
Caution: When using ECMP-LAG on a HNB-GW, this configuration is mandatory for standalone HNB-GW deployment and highly recommended in other deployment scenarios where HNB-GW is used in combination with other services.To monitor or clear subscriber session information filtered by on IMSI/MIN refer to the show subscribers msid command.
Important: This command must be executed at startup only and will not take effect when reconfigured without rebooting.fa-spi-list fa_spi_list
Creates an instance of a Global Title Translation (GTT) address-map, a database, for global titles (ISDN-type address) used for SCCP routing. Upon creating the instance, the system enters global title translation address-map configuration mode. For the commands to configure the database, go to the Global Title Translation Address-Map Configuration Mode Commands chapter.
instance must be an integer from 1 through 4096.
Creates an instance of a Global Title Translation (GTT) association which defines the rules for handling global title translation. Upon creating the instance, the system enters global title translation association configuration mode. For the commands to configure the rules, go to the Global Title Translation Association Configuration Mode Commands chapter.
instance must be an integer from 1 through 16.
gtpp compression-process max_number
max_number: must be an integer from 1 through 4.
gtpp ram-disk-limit mb mega_bytes
mb mega_bytes
mega_bytes: must be an integer from 10 through 256. The default is 32 MB.
If private-extensions is not configured, all customer specific private extensions related to GTPP message transfer with CGF and recovery through GSS are disabled.
Important: In order for the customer-specific extensions to work properly, the gtpp max-pdu-size command in the Context Configuration Mode should be set to 65400 and the gtpp server command’s max value should be set to “1”.
Caution: Entering this command while PDP contexts are in process could cause the loss of pending CDRs. The configuration must be saved and the chassis reloaded for this option to take effect.
Caution: This command must be entered prior to the configuration of other services. Specifying it later may return an error due to a lack of CPU availability.ha-spi-list ha_spi_list
storage-policy name
Specifies a name for an HD storage policy and then enters the HD Storage Policy Configuration Mode. name must be an alphanumeric string of 1 through 63 characters.
The following command creates an HD storage policy named policy3 and enters the HD Storage Policy Configuration Mode:
Default: normal
|
•
|
aggressive: Initiates packet processing card failover without performing additional checks.
|
|
•
|
normal: Initiates packet processing card failover after additional checks are performed.
|
The following command sets the fault detection speed for packet processing card tasks to aggressive:
To allow a chassis to run in PSC/PSCA hybrid-mode with encryption services disabled you must configure hybrid-mode force once.
To go from hybrid mode to non-hybrid mode, you must enter the no hybrid-mode force command. Non-hybrid chassis mode allows encryption services to be started through the appropriate CLI commands. However, all PSCAs in the chassis will be disabled.
For additional information, see the ASR 5000 Installation Guide.
[ no ] imei-profile imei_profile_name
Use this command to create an instance of an IMEI profile and to enter the IMEI Profile Configuration mode. An IMEI profile is a template which groups a set of device instructions, such as blacklisting, that may be applicable to one or more calling devices. See the IMEI Profile Configuration Mode Commands chapter for information regarding the definition of the rules contained within the profile and the use of the profile.
Important: An IMEI profile is a key element of the Operator Policy feature and is only valid when associated with at least one operator policy.To see what IMEI profiles have already been created, return to the Exec mode and enter the show imei-profile all command.
key key_value
Important: This is a customer-specific command that is available for HA, PDSN, EHA, and PDIF. Please contact your local Cisco sales representative for more information.Sets the license key even if resources are not available. The system supports the dynamic resizing of demultiplexor software tasks based on the licensed session capacity and feature type. When installing a license, the system automatically attempts to resize currently functioning tasks. Warning messages are displayed if there is an issue. Though its use is not recommended, the -force keyword can be used to suppress these warning messages.
Caution: Use of this option is not recommended.license key sampleKeyValue
link-aggregation system-priority priority
priority is a hexadecimal value from 0x0000 through 0xFFFF.
For additional usage and configuration information for the link aggregation feature, go to Configuring Link Aggregation in the System Administration Guide.
Important: Not supported on all platformsSpecifies name of the local QoS policy service as an alphanumeric string of 1 through 63 characters.
Important: The name must be unique across all contexts.
Important: This feature is license dependent. Please contact your local sales representative for more information.
Important: A maximum of 16 local QoS policy services are supported.Local Policy Service Configuration Mode commands are defined in the Local Policy Service Configuration Mode Commands chapter.
The following command creates a local QoS policy service named lctest and enters the Local Policy Service Configuration Mode:
Specifies the amount of time (in minutes) that must elapse before a previously locked-out local-user account can attempt to login again. time is an integer from 1 through 10080.
The following command configures a lockout time of 120 minutes (2 hours):
local-user max-failed-logins number
Specifies the maximum number of times a local-user could experience a login failure before their account is locked out. number is an integer from 2 through 100.
Important: Local-user accounts can be configured to either enforce or reject a lockout due to the maximum number of failed login being reached. Refer to the local-user username command for more information.Refer to the local-user lockout-time command for more information.
local-user password { [ complexity { ansi-t1.276-2003 | none } ] [ history length number [ duration days ] ] [ max-age days ] [ min-change-char number ] [ min-change-interval days ] [ min-length number ] }
|
•
|
ansi-t1.276-2003: If this option is selected, the following rules are enforced:
|
|
•
|
none: No additional password checks are performed.
|
number is the number of entries for each account stored in the history list entered as an integer from 1 through 100. days is the number of days during which a password can not be reused entered an integer from 1 through 365.
Important: Local-user accounts can be configured to either enforce or reject a lockout due to a password’s maximum age being reached. Refer to the local-user username command for more information.days is the number of days that passwords remain valid entered as an integer from 1 through 365.
Important: Changes in password length are counted as “character” changes. For example: changing a password from “password” to “passwo” is a 2-character change, changing a password from “password” to “password2” is a 1-character change, and changing a password from “password” to “apassword” is a 9-character change.number is the number of characters entered as an integer from 0 through 16.
days is the minimum number of days that must pass before a user can change their password. It is an integer from 1 through 365.
Important: If the no local-user password min-change-interval command is used, users may change their password as often as desired which could allow them to circumvent the password history function.number is the minimum number of alphanumeric characters that the password must contain, entered as an integer from 3 through 32.
The following command configures the system to store the 4 most recently used passwords per user-account in the history list:
local-user username name [ authorization-level { administrator | inspector | operator | security-admin } ] [ ecs | noecs ] [ ftp | noftp ] [ timeout-min-absolute time ] [ timeoute-min-idle time ] [ no-lockout-login-failure ] [ no-lockout-password-aging ] password password
|
•
|
administrator: Administrator users have read-write privileges and can execute any command throughout the CLI except for a few security functions allowed only in the administrator mode. Administrators can configure or modify the system and are able to execute all system commands, including those available to the operator and inspector user. This level corresponds to the both the System Administrator and Application Administrator levels in the T1.276-2003.
|
|
•
|
inspector: Inspector users are limited to a small number of read-only Exec Modecommands.The bulk of these are “show” commands giving the inspector the ability to view a variety of statistics and conditions. The Inspector cannot execute show configuration commands and do not have the privilege to enter the Config Mode.
|
|
•
|
operator: Operator users have read-only privileges to a larger subset of the Exec Mode commands as depicted in the following figure. Operator users can execute all commands that are part of the inspector mode, plus some system monitoring, statistical, and fault management functions. Operators do not have the ability to enter the Config Mode.
|
|
•
|
security-admin: Security Administrator users have read-write privileges and can execute any command throughout the CLI. Security Administrators can execute all system commands, including those available to the administrator, operator, and inspector users. This level corresponds to both the System Security Administrator and Application Security Administrator levels in T1.276-2003.
|
|
•
|
ecs: The user has access.
|
|
•
|
noecs: The user does not have access.
|
Default: ecs
|
•
|
ftp: The user has access.
|
|
•
|
noftp: The user does not have access.
|
Specifics the maximum session time (in minutes) for this user. time is an integer from 0 through 525600. A value of “0” indicates no limit.
Important: This limit applies only to the user’s CLI sessions.Specifics the maximum idle time (in minutes) for this user. time is an integer from 0 through 525600. A value of “0” indicates no limit.
Important: This limit applies only to the user’s CLI sessions.password password
Specifies the initial password for this user. password must an alphanumeric string of 6 through 32 characters that is case sensitive.
Important: The user is requested to change their password upon their first login.The following command configures a security-administrator level local-user administrative account for a user named User672 that has FTP privileges, a temporary password of abc123, and that does not lockout due to either login attempt failures or password aging:
eventid id
Specifies the event for which no logging is to occur. id must be a integer from 1 through 100000.
to to_id
Specifies the end ID of the events when a range of event ID is to be disabled from being logged. to_id must be an integer from 1 through 100000. The to_id must be equal to or larger than the id specified.
event-verbosity evt_level
|
•
|
|
•
|
|
•
|
pdu-data format
Specifies output format for packet data units when logged as one of:
|
•
|
none: outputs in raw format
|
|
•
|
hex; displays out in hexadecimal format
|
|
•
|
hex-ascii; displays output in hexadecimal and ASCII similar to a main-frame dump
|
pdu-verbosity pdu_level
The following command sets the logging display level of detail for packet data units to level 3 and sets the output format to the main-frame style hex-ascii:
facility facility
|
•
|
a10: A10 interface facility
|
|
•
|
a11: A11 interface facility
|
|
•
|
a11mgr: A11 Manager facility
|
|
•
|
aaa-client: AAA client facility
|
|
•
|
aaamgr: AAA manager logging facility
|
|
•
|
aaaproxy: AAA Proxy facility
|
|
•
|
aal2: AAL2 protocol logging facility
|
|
•
|
acl-log: Access Control List logging facility
|
|
•
|
acsctrl: Active Charging Service (ACS) Controller facility
|
|
•
|
acsmgr: Active Charging Service (ACS) Manager facility
|
|
•
|
alarmctrl: Alarm Controller facility
|
|
•
|
alcap: ALCAP protocol logging facility
|
|
•
|
alcapmgr: ALCAPMgr logging facility
|
|
•
|
all: All facilities
|
|
•
|
asngwmgr: ASN Gateway Manager facility
|
|
•
|
asnpcmgr: ASN Paging Controller Manager facility
|
|
•
|
bfd: BFD protocol logging facility
|
|
•
|
bgp: Border Gateway Protocol (BGP) facility
|
|
•
|
bindmux: IPCF BindMux-De-mux Manager logging facility
|
|
•
|
bssap+: Base Station Sub-system Application Part+ protocol facility for the login interface between the SGSN and the MSC/VLR (2.5G and 3G)
|
|
•
|
bssgp: Base Station Sub-system GPRS Protocol logging facility handles exchange information between the SGSN and the BSS (2.5G only)
|
|
•
|
callhome: Call home application logging facility
|
|
•
|
cap: CAMEL Application Part (CAP) logging facility for protocol used in prepaid applications (2.5G and 3G)
|
|
•
|
cli: CLI logging facility
|
|
•
|
credit-control: Credit Control facility
|
|
•
|
cscf: IMS/MMD CSCF
|
|
•
|
cscfmgr: SIP CSCF Manager facility
|
|
•
|
cscfttmgr: SIP CSCFTT Manager facility
|
|
•
|
csp: Card Slot Port controller facility
|
|
•
|
css: Content Service Selection (CSS) facility
|
|
•
|
css-sig: Content Service Selection (CSS) RADIUS Signaling facility
|
|
•
|
cx-diameter: Cx Diameter Messages facility
|
|
•
|
dcardctrl: IPSEC Daughter Card Controller logging facility
|
|
•
|
dcardmgr: IPSEC Daughter Card Manager logging facility
|
|
•
|
demuxmgr: Demux Manager API facility
|
|
•
|
dgmbmgr: Diameter Gmb Application Manager logging facility
|
|
•
|
dhcp: Dynamic Host Configuration Protocol logging facility
|
|
•
|
dhcpv6: DHCPv6
|
|
•
|
dhost: Distributed Host logging facility
|
|
•
|
diabase: Diabase messages facility
|
|
•
|
diameter: Diameter endpoint logging facility
|
|
•
|
diameter-acct: Diameter Accounting
|
|
•
|
diameter-auth: Diameter Authentication
|
|
•
|
diameter-dns: Diameter DNS subsystem
|
|
•
|
diameter-ecs: ACS Diameter signaling facility
|
|
•
|
diameter-hdd: Diameter HDD Interface facility
|
|
•
|
diameter-svc: Diameter Service
|
|
•
|
diamproxy: DiamProxy logging facility
|
|
•
|
dpath: IPSEC Data Path facility
|
|
•
|
drvctrl: Driver Controller facility
|
|
•
|
eap-ipsec: EAP
|
|
•
|
eap-sta-s6a-s13-s6b-diameter: EAP/STA/S6A/S13/S6B Diameter messages facility
|
|
•
|
ecs-css: ACSMGR <-> Session Manager Signalling Interface facility
|
|
•
|
egtpc: eGTP-C logging facility
|
|
•
|
egtpmgr: eGTP manager logging facility
|
|
•
|
egtpu: eGTP-U logging facility
|
|
•
|
epdg: ePDG logging facility
|
|
•
|
evlog: Event log facility
|
|
•
|
famgr: Foreign Agent manager logging facility
|
|
•
|
firewall: Firewall logging facility
|
|
•
|
fng: FNG logging facility
|
|
•
|
gmm:
|
|
•
|
gprs-app: GPRS Application logging facility
|
|
•
|
gprs-ns: GPRS Network Service Protocol (layer between SGSN and the BSS) logging facility
|
|
•
|
gq-rx-tx-diameter: Gq/Rx/Tx Diameter messages facility
|
|
•
|
gss-gcdr: GTPP Storage Server GCDR facility
|
|
•
|
gtpc: GTP-C protocol logging facility
|
|
•
|
gtpcmgr: GTP-C protocol Manager logging facility
|
|
•
|
gtpp: GTP-PRIME protocol logging facility
|
|
•
|
gtpu: GTP-U protocol logging facility
|
|
•
|
gtpumgr: GTPU Demux manager
|
|
•
|
gx-ty-diameter: Gx/Ty Diameter messages facility
|
|
•
|
gy-diameter: Gy Diameter messages facility
|
|
•
|
hamgr: Home Agent manager logging facility
|
|
•
|
hat: High Availability Task (HAT) process facility
|
|
•
|
hdctrl: HD Controller logging facility
|
|
•
|
hnb-gw: HNB-GW (3G Femto GW) logging facility
|
|
•
|
hnbmgr: HNBMGR (3G Femto GW DemuxMgr) logging facility
|
|
•
|
hss-peer-service: HSS Peer Service facility
|
|
•
|
igmp: IGMP
|
|
•
|
ikev2: IKEv2
|
|
•
|
ims-authorizatn: IMS Authorization Service facility
|
|
•
|
ims-sh: HSS SH Service facility
|
|
•
|
imsimgr: SGSN IMSI Manager facility
|
|
•
|
imsue: IMSUE
|
|
•
|
ip-arp: IP Address Resolution Protocol facility
|
|
•
|
ip-interface: IP interface facility
|
|
•
|
ip-route: IP route facility
|
|
•
|
ipms: IPMS logging facility
|
|
•
|
ipsec: IP Security logging facility
|
|
•
|
ipsg: IP Service Gateway interface logging facility
|
|
•
|
ipsgmgr: IP Services Gateway facility
|
|
•
|
ipsp: IP Pool Sharing Protocol logging facility
|
|
•
|
kvstore: KV Store facility
|
|
•
|
l2tp-control: L2TP control logging facility
|
|
•
|
l2tp-data: L2TP data logging facility
|
|
•
|
l2tpdemux: L2TP Demux Manager logging facility
|
|
•
|
l2tpmgr: L2TP Manager logging facility
|
|
•
|
lagmgr: LAGMGR logging facility
|
|
•
|
ldap: Lightweight Directory Access Protocol (LDAP) messages logging facility
|
|
•
|
li: Refer to the Lawful Intercept Interface Reference for a description of this command.
|
|
•
|
linkmgr: SGSN/BSS SS7 Link Manager logging facility (2.5G only)
|
|
•
|
llc: Logical Link Control (LLC) Protocol logging facility; for SGSN: logs the LLC layer between the GMM and the BSSGP layers for logical links between the MS and the SGSN
|
|
•
|
local-policy: Local Policy Service facility
|
|
•
|
m3ua: M3UA Protocol logging facility
|
|
•
|
magmgr: Mobile Access Gateway manager logging facility
|
|
•
|
map: MAP Protocol logging facility
|
|
•
|
megadiammgr: Megadiameter Manager (SLF Service) logging facility
|
|
•
|
mme-app: Mobility Management Entity Application logging facility
|
|
•
|
mme-misc: MME miscellaneous logging facility
|
|
•
|
mmedemux: Mobility Management Entity Demux Manager logging facility
|
|
•
|
mmemgr: MME Manager facility
|
|
•
|
mmgr: Master Manager logging facility
|
|
•
|
mobile-ip: Mobile IP processes
|
|
•
|
mobile-ip-data: Mobile IP data facility
|
|
•
|
mobile-ipv6: Mobile IPv6 logging facility
|
|
•
|
mpls: MPLS protocol logging facility
|
|
•
|
mseg-app: MSEG application logging facility
|
|
•
|
mseg-gtpc: MSEG GTPC application logging facility
|
|
•
|
mseg-gtpu: MSEG GTPU application logging facility
|
|
•
|
msegmgr: MSEGMgr (MSEG DemuxMgr) logging facility
|
|
•
|
mtp2: MTP2 Service logging facility
|
|
•
|
mtp3: MTP3 Protocol logging facility
|
|
•
|
multicast-proxy: Multicast Proxy logging facility
|
|
•
|
npuctrl: Network Processor Unit Control facility
|
|
•
|
npumgr: Network Processor Unit Manager facility
|
|
•
|
npumgr-acl: NPUMGR ACL logging facility
|
|
•
|
npumgr-flow: NPUMGR FLOW logging facility
|
|
•
|
npumgr-fwd: NPUMGR FWD logging facility
|
|
•
|
npumgr-init: NPUMGR INIT logging facility
|
|
•
|
npumgr-port: NPUMGR PORT logging facility
|
|
•
|
npumgr-recovery: NPUMGR RECOVERY logging facility
|
|
•
|
ntfy-intf: Notification Interface logging facility
|
|
•
|
orbs: Object Request Broker System logging facility
|
|
•
|
ospf: OSPF protocol logging facility
|
|
•
|
ospfv3: OSPFv3 protocol logging facility
|
|
•
|
p2p: Peer-to-Peer Detection logging facility
|
|
•
|
pccmgr: IPCF PCC Manager library
|
|
•
|
pdg: PDG logging facility
|
|
•
|
pdgdmgr: PDG Demux Manager logging facility
|
|
•
|
pdif: PDIF logging facility
|
|
•
|
pgw: PDN Gateway logging facility
|
|
•
|
phs: Payload Header Suppression
|
|
•
|
phs-control: PHS X1/X5 and X2/X6 Interface logging facility
|
|
•
|
phs-data: PHS Data logging facility
|
|
•
|
phs-eapol: PHS EAPOL logging facility
|
|
•
|
phsgwmgr: PHS Gateway Manager facility
|
|
•
|
phspcmgr: PHS Paging Controller Manager facility
|
|
•
|
pmm-app: PMM application logging facility
|
|
•
|
ppp: PPP link and packet facilities
|
|
•
|
pppoe: PPPOE logging facility
|
|
•
|
push: VPNMGR CDR push logging facility
|
|
•
|
radius-acct: RADIUS accounting logging facility
|
|
•
|
radius-auth: RADIUS authentication logging facility
|
|
•
|
radius-coa: RADIUS change of authorization and radius disconnect
|
|
•
|
ranap: Radio Access Network Application Part (RANAP) Protocol facility logging info flow between SGSN and RNS (3G)
|
|
•
|
rct: Recovery Control Task logging facility
|
|
•
|
rdt: Redirect Task logging facility
|
|
•
|
resmgr: Resource Manager logging facility
|
|
•
|
rf-diameter: Rf Diameter messages facility
|
|
•
|
rip: RIP logging facility (RIP is not supported at this time.)
|
|
•
|
rohc: RObust Header Compression facility
|
|
•
|
rsvp: Reservation Protocol logging facility
|
|
•
|
rua: RUA (3G Femto GW - RUA messages) logging facility
|
|
•
|
s1ap: S1AP Protocol logging facility
|
|
•
|
sccp: SCCP Protocol logging connection-oriented messages between RANAP and TCAP layers.
|
|
•
|
sct: Shared Configuration Task logging facility
|
|
•
|
sctp: SCTP Protocol logging facility
|
|
•
|
sessctrl: Session Controller logging facility
|
|
•
|
sessmgr: Session Manager logging facility
|
|
•
|
sesstrc: session trace logging facility
|
|
•
|
sft: Switch Fabric Task logging facility
|
|
•
|
sgs: SGs protocol logging facility
|
|
•
|
sgsn-app: SGSN-APP logging various SGSN ‘glue’ interfaces, e.g., between PMM, MAP,. GPRS-FSM, SMS.
|
|
•
|
sgsn-failures: SGSN call failures (attach/activate rejects) logging facility (2.5G)
|
|
•
|
sgsn-gtpc: SGSN GTP-C Protocol logging control messages between the SGSN and the GGSN
|
|
•
|
sgsn-gtpu: SGSN GTP-U Protocol logging user data messages between the SGSN and GGSN
|
|
•
|
sgsn-mbms-bearer: SGSN MBMS Bearer app (SMGR) logging facility
|
|
•
|
sgsn-misc: Used by stack manager to log binding and removing between layers
|
|
•
|
sgsn-system: SGSNs System Components logging facility; used infrequently
|
|
•
|
sgsn-test: SGSN Tests logging facility; used infrequently
|
|
•
|
sgtpcmgr: SGSN GTPC Manager logging information exchange through SGTPC and the GGSN
|
|
•
|
sgw: Serving Gateway facility
|
|
•
|
sh-diameter: Sh Diameter messages facility
|
|
•
|
sitmain: System Initialization Task main logging facility
|
|
•
|
sm-app: SM Protocol logging facility
|
|
•
|
sms: Short Message Service (SMS) logging messages between the MS and the SMSC
|
|
•
|
sndcp: SNDCP Protocol logging facility
|
|
•
|
snmp: SNMP logging facility
|
|
•
|
sprmgr: IPCF SPR Manager logging facility
|
|
•
|
srdb: Static Rating Database
|
|
•
|
srp: Service Redundancy Protocol (SRP) logging facility
|
|
•
|
sscfnni: SSCFNNI Protocol logging facility
|
|
•
|
sscop: SSCOP Protocol logging facility
|
|
•
|
ssh-ipsec: SSH IP Security logging facility
|
|
•
|
ssl: SSL (Secure socket layer messages) logging facility
|
|
•
|
stat: Statistics logging facility
|
|
•
|
system: System logging facility
|
|
•
|
tacacsplus: TACACS+ Protocol logging facility
|
|
•
|
tcap: TCAP Protocol logging facility
|
|
•
|
testctrl: Test Controller logging facility
|
|
•
|
testmgr: Test Manager logging facility
|
|
•
|
threshold: threshold logging facility
|
|
•
|
ttg: TTG logging facility
|
|
•
|
tucl: TUCL logging facility
|
|
•
|
udr: User detail record facility (used with the Charging Service)
|
|
•
|
user-data: User data logging facility
|
|
•
|
user-l3tunnel: User layer-3 tunnel logging facility
|
|
•
|
usertcp-stack: User TCP Stack
|
|
•
|
vpn: Virtual Private Network logging facility
|
|
•
|
wimax-data: WiMAX DATA
|
|
•
|
wimax-r6: WiMAX R6
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
critical-info | no-critical-info: indicates if critical information is to be displayed or not. The keyword critical-info specifies that events with a category attribute of critical information are to be displayed. Examples of these types of events can be seen at bootup when system processes and tasks are being initiated. The no-critical-info keyword specifies that events with a category attribute of critical information are not to be displayed.
Caution: Issuing this command could negatively impact system performance depending on system loading, the log level, and/or the type of facility(ies) being logged.ipaddr ip_address
Specifies the IP address of the user for which the monitoring filter is to be set. ip_address must entered using IPv4 dotted-decimal notation.
msid ms_id
msid ms_id: specifies the mobile subscriber ID for which the monitoring filter is to be set. ms_id must be from 7 to 16 digits.
username user_name
username user_name: specifies a user for which the monitoring filter is to be set. user_name must refer to a previously configured user.
Caution: Issuing this command could negatively impact system performance depending on the number of subscribers for which monitoring is performed and/or the amount of data they’re passing.The following command enables the monitoring of user user1 and mobile subscriber ID 4441235555, respectively.
|
•
|
all-events: Logging daemon runtime buffer stores all logs that come to it.
|
|
•
|
filtered-events-only: Logging daemon runtime buffer stores only logs that pass the runtime filter.
|
This command enters the LTE Policy Configuration Mode where LTE policy parameters can be configured.
LTE Policy Configuration Mode commands are defined in the LTE Policy Configuration Mode Commands chapter.
Important: This command is not supported in this release. For more information please contact your Cisco account representative.Also see the MSEG Global Configuration Mode Commands chapter.
network-overload-protection sgsn-new-connections-per-second #_new_connections action { drop | reject with cause { congestion | network failure } } [ queue-size queue_size ] [ wait-time wait_time ]
Using default in the command, disables this attach rate throttle feature that provides network overload protection.
sgsn-new-connections-per-second #_new_connections
#_new_connections: Must be an integer from 50 to 5000.
|
•
|
drop: Drop the new connection request.
|
|
•
|
reject-with-cause: Reject the new connection request. Include one of the following as the cause in the reject message:
|
queue-size queue_size
Defines the maximum size of the pacing queue used for buffering the packets. If configured, the queue-size should be greater than or equal to the #_new_connections value and less than or equal to the optimal value (the wait_time * #_new_connections). This validation is done in the CLI.
queue_size Must be an integer from 250 to 25000.
Default: unconfigured. The default value is the #_new_connections * wait-time. This will be the optimal value.
wait-time wait_time
wait_time Must be an integer from 1 to 15
The SGSN’s optimized network overload protection performs attach-rate throttling to avoid overloading Gr, Gn and Gf interfaces. This is enabled with queue-size and wait-time keywords so that the IMSIMgr throttles the attach rate to values configured with these keywords.
Counters for this feature are available in the show gmm-sm statistics command display in the Network Overload Protection portion of the table.
Set the attach rate to 500 per second, the action to drop, the wait time to 5 seconds, and the queue size to be calculated (as follows: wait_time * #_new_connections - i.e., 2500)
[local]<hostname>(nse-fr-peer-nsei-<peer_nsei_number>)#
Important: If the use of NTP is disabled the system clock may drift over a period of time. This may require manual updates to the system clock to synchronize the clock with other network elements.This command creates an operator policy and enters the operator policy configuration mode. Commands for configuration of the policies are available in the Operator Policy Configuration Mode Commands chapter.
default, in this case, is the name of a specific operator policy. This default policy is used when no other defined operator policy matches the incoming IMSI.
Important: You should configure this default operator policy to be it available to handle IMSIs that are not matched with other defined policies.name policy_name
Specifies the unique name of an operator policy. policy_name is entered as an alphanumeric string of 1 through 64 characters.
The system supports up to 1,000 operator policies, including the default operator policy.
Important: An operator policy is the key element of the Operator Policy feature. After defining an instance of an operator policy, you must go to the SGSN Global Configuration Mode (from the Global Configuration mode) to define the IMSI range(s). This requirement does not hold if you are using a default operator policy.To see what operator policies have already been created, return to the Exec mode and enter the show operator-policy all command.
This command has been renamed to card-standby-priority. Please refer to that command for details. Note that for backwards compatibility, the system accepts this command as valid.
port atm slot/port
slot: Identifies the chassis slot holding the line card that supplies ATM ports. The slot ID number can be an integer from 17 through 48.
port: Identifies the physical port that is to be configured to support ATM signaling. The ID number can be an integer from 1 through 4.
Important: This command is not supported on all platforms.port bits slot/port
slot: Identifies the chassis slot holding the SPIO. The slot ID can be either 24 (active SPIO) or 25 (standby SPIO).
port: Identifies the BITS port on the SPIO. The port ID number must be 4.
Important: This command is not supported on all platforms.Identifies a physical port on a Channelized Line Card (CLC) that supports Frame Relay signaling and creates a Frame Relay interface. This command enters the configuration mode for the commands that configure the Frame Relay interface and the channelized port interface. For additional information, see the Channelized Port Configuration Mode Commands chapter.
port channelized slot/port
To determine valid slots and port numbers, use the Exec mode’s command show port table to find the channelized line card.
slot: Identifies the chassis slot holding the Channelized Line Card that sources Frame Relay ports. The slot ID number can be an integer from 17 through 48.
port: Identifies the physical port that is to be configured to support Frame Relay signaling. The ID number can only be 1.
port ethernet slot/port
port mac-address virtual-base-address MAC_Address
Caution: This configuration requires the configuration of a valid block of unique MAC addresses that are not used anywhere else. Use of non-unique MAC addresses can degrade and impair the operation of your network.
Important: This command is not supported on all platforms.To enable virtual MAC addressing for Ethernet ports on all Ethernet line cards in the system using a block of MAC addresses starting at 00:05:47:FF:00:00, enter the following command:
slot 3
The value for slot must be either 24 or 25.
Creates a new or enters an existing mapping table configuration. name must be an alphanumeric string of 1 through 63 alphanumeric.
QCI Mapping Configuration Mode commands are defined in the QCI Mapping Configuration Mode Commands chapter.
Important: This command creates a mapping table available to any HSGW context configured on the system.The following command will remove qci_table1 from the system:
no ps-network ps_instance
Caution: Removing the HNB-PS network instance is a disruptive operation and it will affect all UEs accessing SGSN(s) in specific PS core network through the HNB-GW service.
Warning: If any HNB-PS Network instance is removed from system all parameters configured in that mode will be deleted and Iu-PS/Iu-Flex interface will be disabled.Specifies the name of the Packet Switched Core Networks instance which needs to be associated with HNB Radio Network PLMN in HNB RN-PLMN configuration mode. If ps_instance does not refer to an existing HNB-PS instance, the new HNB-PS network instance is created.
ps_instance must be an alphanumeric string of 1 through 63 characters.
Caution: This is a critical configuration. The HNBs can not access SGSNs in PS core network without this configuration. Any change to this configuration would lead to disruption in HNB access to PS core network.The various parameters available for configuration of an HNB-PS network instance are defined in the HNB-PS Network Configuration Mode Commands chapter.
The following command will remove HNB-PS network instance hnb-ps1 from the system without any prompt to user:
Creates a new or enters an existing mapping configuration. name must be an alphanumeric string of 1 through 63 characters.
QCI - QoS Mapping Configuration Mode commands are defined in the QCI - QoS Mapping Configuration Mode Commands chapter.
Important: This command creates a mapping configuration available to any HSGW, P-GW, S-GW context configured on the system.qos npu inter-subscriber traffic bandwidth gold percent silver percent bronze percent best-effort percent
gold percent
percent can be configured to an integer from 0 through 100.
silver percent
percent can be configured to an integer from 0 through 100.
bronze percent
percent can be configured to an integer from 0 through 100.
best-effort percent
percent can be configured to an integer from 0 through 100.
Important: This functionality is not supported for use with the PDSN at this time.qos npu inter-subscriber traffic bandwidth-sharing { { enable | disable } { all | slot slot_num cpu cpu_num } }
slot slot_num
slot_num is the slot in which a packet processing card is installed. These cards can be installed in slots 1 through 8, and/or 10 through 16.
cpu cpu_num
cpu_num is an integer value from 0 to 3. 0 represents the lead CP.
For additional information on the NPU QoS functionality, refer to the System Administration Guide.
Important: This functionality is not supported for use with the PDSN at this time.afXX
Assigns the Assured Forwarding XX PHB (per-hop behavior) DSCP.
For additional information on the NPU QoS functionality, refer to the System Administration Guide.
Important: This functionality is not supported for use with the PDSN at this time.Specifies the name of the RAN Peer Map. name must be an alphanumeric string of 1 through 31 characters.
Important: In 8.1 and later releases, this keyword is not supported.
Important: In 8.0 and earlier releases and in 9.0 and later releases, this keyword is not supported.
Important: In Release 8.1, ACS must be configured in the Optimized mode.
Important: In Release 8.1, if the active-charging mode is changed from the default (non-optimized) mode to the Optimized mode, or vice-versa, the system must be rebooted for the change to take effect.
Important: In Release 8.3, this keyword is obsolete. With or without this keyword ACS is always enabled in the Optimized mode.Use the require active-charging command to enable ACS in the non-optimized mode. Wherein, ACS Managers will spawn to support ACS.
Use the require active-charging optimized-mode command to enable ACS in the Optimized mode. Wherein, ACS is enabled as part of Session Managers.
For Dynamic Content Filtering support, the static-and-dynamic keyword must be configured to specify that the Dynamic Rater Package (model and feature files) must be distributed to rating modules on startup, recovery, etc. If not configured, by default, the static-only mode is enabled.
Important: This command triggers the resource subsystem to switch to ACS-enabled mode and start ACS-related tasks. This CLI command must be configured before any services are configured, so that the resource subsystem can appropriately reserve adequate memory for the ACS-related tasks. After configuring this command, the configuration must be saved and the system rebooted in order to allocate the resources for ACS upon system startup.require cipher ssl resource-percentage percentage_value
Important: This command is not supported on all platforms.If this command is not configured, or the no require ecs credit-control subscriber-mode command is configured, DCCA/Gy sessions are created per bearer/PDP-context, and as a result when there are multiple PDP contexts or multiple bearers in a PDN as many DCCA/Gy sessions are created.
Important: This command will take effect only when the system is booted/rebooted. When configured after the system comes up, the command will be accepted but will not be applied until after the system is rebooted with the saved configuration.
Important: This command is independent of the require active-charging command. The ecs keyword in this command is license dependent.The no option of this command disables this feature.
This command only works when the Session Recovery feature is enabled through a valid Session and Feature Use License Key.
Important: After entering this command, you must restart the system for the command takes effect. Remember to save the configuration file before issuing the reload command.Enables the input of commands for features that do not have license keys installed. The output of the command show cli indicates when this is enabled. This command effects all future CLI sessions. This is disabled by default.
rohc-profile profile-name name [ -noconfirm ] [ common-options | compression-options | decompression-options ]
The name of the RoHC profile to create or remove. name must be an alphanumeric string of 1 through 63 characters.
RoHC Profile Configuration Mode commands are defined in the RoHC Profile Configuration Mode Commands chapter.
Enter the following command to create an RoHC profile named HomeUsers and enter the RoHC Configuration mode without prompting for verification:
no sccp-network sccp_net_id
Remove the SCCP network configuration with the specified index number from the system configuration.
sccp_net_id: must be an integer from 1 through 12.
For details about the commands and parameters needed to create and edit the SCCP Network configuration, check the SCCP Network Configuration Mode chapter.
The following command creates an SCCP network with the index number of 2 to associate with HNB-GW service for HNB access network users without any prompt.:
Specifies the name of the SCTP parameter template being created or accessed. name must be an alphanumeric string of 1 through 63 characters.
SCTP Parameter Template Configuration Mode commands are defined in the SCTP Parameter Template Configuration Mode Commands chapter.
The following command creates a new SCTP parameter template or enters an existing template named sctp-tmpl2:
session trace network-element { all | mme | pgw | sgw | ggsn } [ collection-timer sec ] [ tce-mode { none | push transport sftp path string username name { encrypted password enc_pw | password password } } ]
all: Specifies that all network elements and their associated interfaces are to be made available to the session trace application.
ggsn: Specifies that the GGSN as network element and its associated interfaces is to be made available to the session trace application.
mme: Specifies that the MME as network element and its associated interfaces is to be made available to the session trace application.
pgw: Specifies that the P-GW as network element and its associated interfaces is to be made available to the session trace application.
sgw: Specifies that the S-GW as network element and its associated interfaces is to be made available to the session trace application.
collection-timer sec
Specifies the amount of time (in seconds) to wait from initial activation/data collection before data is reported to the Trace Collection Entity (TCE). sec must be an integer from 0 through 255.
tce-mode push transport sftp path string username name { encrypted password enc_pw | password password }
sftp: Specifies that Secure FTP is used to push session trace files to the TCE.
path string: Specifies the directory path on the TCE where files will be placed.
username name: Specifies the username to be used when pushing files to the TCE.
encrypted password enc_pw: Specifies the encrypted password to be used when pushing files to the TCE.
password password: Specifies the password to be used when pushing files to the TCE.
The following command configures the collection time for session traces to 30 seconds, identifies the network element as all elements (GGSN, MME, S-GW, and P-GW), and pushes session trace files to a TCE via SFTP into a directory named /trace/agw using a username admin and a password of pw123:
The following command configures the collection time for session traces to 30 seconds, identifies the network element as an MME, and pushes session trace files to a TCE via SFTP into a directory named /trace/sgw using a username admin and a password of pw123:
The following command configures the collection time for session traces to 30 seconds, identifies the network element as GGSN, and pushes session trace files to a TCE via SFTP into a directory named /trace/ggsn using a username admin and a password of pw123:
no snmp community string
Specifies a community string whose options are to be modified. string must be an alphanumeric string of 1 through 31 characters.
context ctx_name
Specifies a the context to which the community string shall be applied. ctx_name must be an alphanumeric string of 1 through 1023 characters.
view view_name
Specifies the view to which the community string shall be applied. view_name must be an alphanumeric string of 1 through 1023 characters.
read-only | read-write
read-only: the configuration may only be viewed.
read-write: the configuration may be viewed and edited.
snmp community sampleString
no snmp community sampleString
Specifies the SNMPv3 engine to employ. id must be an alphanumeric string of 1 through 31 characters.
Important: The system can send either SNMPv1, SNMPv2c, or SNMPv3 traps to numerous target devices. However, the Web Element Manager can only process SNMP version 1 (SNMPv1) and SNMP version 2c (SNMPv2c) traps. If the SNMP target being configured is Web Element Manager application, then you must not configure this command to use.Specifies the interval time (in minutes) between notifications. minutes must be an integer from 1 through 1440.
Specifies the secondary interval time, in seconds, between notifications. seconds must be an integer from 10 through 50.
Specifies the number of notifications that must be generated before the next notification is broadcast to SNMP users. count must be an integer from 1 through 10000.
low low_count
Specifies the number of notifications within the monitoring period before which any subsequent notification for each specific event. low_count must be an integer from 1 through 10000.
period seconds
Specifies the number of seconds of the monitoring window size before any subsequent notification may be broadcast to users. seconds must be an integer from 10 through 3600.
port number
Specifies the port number to use for SNMP communications. number must be an integer from 1 to 65535.
Important: This will result in restarting the SNMP agent when the no keyword is omitted. SNMP queries as well as notifications/traps will be blocked until the agent has restarted.snmp target name ip_address [ port number ] [ non-default ] [ security-name string ] [ version { 1 | 2c | 3 | view ] [ security-level { noauth | { auth | priv-auth privacy [ encrypted ] des privpassword } authentication [ encrypted ] { md5 | sha } authpassword } } [ informs | traps ]
no snmp target name
authentication { md5 | sha } authpassword
Reads the authentication type and password if the security level of the SNMP messages is set to auth or priv-auth. Authentication types are:
|
•
|
md5: Configures the hash-algorithm to implement MD5 per RFC 1321.
|
|
•
|
sha: Specifies that the hash protocol is Secure Hash Algorithm.
|
|
•
|
noauth: No authentication and encryption is used.
|
|
•
|
auth: Only authentication will be used.
|
|
•
|
priv-auth: Both authentication and encryption will be used.
|
|
•
|
privacy des privpassword: Reads the privacy type and password.
|
Specifies a logical name to use to refer to the remote receiver. name must be an alphanumeric string of 1 through 31 characters.
Specifies the IP address of the receiver. ip_address must be specified using IPv4 dotted-decimal notation.
Specifies that this destination is only used for SNMP traps which have been specifically identified.
port number
Specifies the port which is to be used in communicating with the remote receivers. number must be an integer from 0 through 65535.
security-name string
Specifies the community string to use in the unsolicited messages. string must be an alphanumeric string of 1 through 31 characters.
Important: The system can send either SNMPv1, SNMPv2c, or SNMPv3 traps to numerous target devices.However, the Web Element Manager can only process SNMP version 1 (SNMPv1) and SNMP version 2c (SNMPv2c) traps. If the SNMP target being configured is Web Element Manager application, then you must configure this command to use version 1 or version 2c.informs | traps
Specifies the type of SNMP event to use to send notifications to SNPM targets. traps are unacknowledged (fire and forget) whereas informs require a response from the SNMP target.
If the notification type is set to informs, the notification is resent if no response is received within 5 seconds. The notification is resent at most two times.
no snmp target sampleReceiver
Important: The system disregards character case (case insensitive) when entering trap names.SNMP traps are used by the system to indicate that certain events have occurred. A complete listing of the traps supported by the system and their descriptions can be found in the SNMP MIB Reference. Additionally, a trap listing can be viewed using the following command:
Important: If the Web Element Manager application is used as your alarm server, the application relies on the timestamp provided by enabling this command to identify duplicate traps. As a result, it is recommended that this parameter be enabled for this case.snmp user user_name [ [ encrypted ] password password | engine id | group grp_name | security-model model auth [ [ encrypted ] password password ] ]
no snmp user user_name
Specifies the user which is to use SNMPv3 interfaces to the system. user_name must be an alphanumeric string of 1 through 31 characters.
engine id
The SNMP engine ID. id must be an alphanumeric string of 1 through 31characters.
group grp_name
Specifies the user SNMPv3 group the into which user will be added. grp_name must be an alphanumeric string of 1 to 1023 characters.
Specifies the security model used to authenticate the user. model must be configured to the following:
|
•
|
usm: User Security Model
|
The encrypted keyword indicates the password will be received in an encrypted form. password must be an alphanumeric string of 8 through 31 characters.
The encrypted keyword is intended only for use by the chassis while saving configuration scripts. The system displays the encrypted keyword in the configuration file as a flag that the variable following the password keyword is the encrypted version of the plain text password. Only the encrypted password is saved as part of the configuration file.
Important: The system can send either SNMPv1, SNMPv2c, or SNMPv3 traps to numerous target devices. However, the Web Element Manager can only process SNMP version 1 (SNMPv1) and SNMP version 2c (SNMPv2c) traps. If the SNMP target being configured is Web Element Manager application, then you must not configure this command to use.no ss7-routing-domain rd_id
Identifies a specific SS7 routing domain. Once it has been created, it can be accessed for further configuration and modification by entering the rd_id without entering the variant.
rd_id must be an integer from 1 through 12.
variant v_type
|
•
|
ansi: American National Standards Institute (U.S.A.)
|
|
•
|
bici: Broadband Intercarrier Interface standard
|
|
•
|
china: Chinese standard
|
|
•
|
itu: International Telecommunication Union (ITU-T) Telecommunication Standardization Sector
|
|
•
|
ntt: Japanese standard
|
|
•
|
ttc: Japanese standard
|
For details about the commands and parameters used to define or edit an SS7 routing domain, refer SS7 Routing Domain Configuration Mode chapter.
The following creates an SS7 routing domain with an index of 1 and the variant selection of Broadcast Intercarrier Interface (bici):
The following command creates an SS7 routing domain instance with an index of 2 and the variant selection of Broadcast Intercarrier Interface (bici) to be associated with HNB RN-PLMN in an HNB access network:
system { carrier-id mcc mcc_id mnc mnc_id | contact who | description string | hostname host_name | location text| sysdesc-sysoid-style [ default | new ] }
Important: This carrier ID is not used by the GGSN|
•
|
|
•
|
|
•
|
mcc mcc_id: The mobile country code. This must be specified as a 3-digit string from 001 through 999.
mnc mnc_id: The mobile network code. This must be specified as a 2- or 3-digit string from 01 through 999.
contact who
contact who: specifies the contact information for the chassis. who must be an alphanumeric string of 0 through 255 characters. The string must be embedded in double quotes (“) if spaces and special punctuation is to be used.
description string
|
•
|
%version% - software version.
|
|
•
|
%build% - software build number
|
|
•
|
%chassis% - chassis type (ASR 5000)
|
|
•
|
%staros% - OS type
|
|
•
|
%hostname% - system name
|
|
•
|
%release% - release number
|
|
•
|
%kerver% - kernel version
|
|
•
|
%machine% - machine hardware name
|
|
•
|
string - an alphanumeric string of 1 through 255 characters.
|
hostname host_name
hostname host_name: configures the chassis host name where host_name must be an alphanumeric string of 1 through 63 characters.
Important: Please note that changing the chassis host name results in the command prompt changing as well to reflect the new name. This may affect any previously scripted interfaces from an OSS or maintenance facility.location text
location text: specifies the system location expressed as an alphanumeric string of 0 through 255 characters. The text specified must be embedded in double quotes (“) if spaces are to be used.
|
•
|
default - SNMP returns old style system description and old style system OID string.
|
|
•
|
new - SNMP returns Cisco style system description and Cisco style OID string.
|
Enter TACACS Configuration Mode to configure up to three TACACS+ servers for use in authenticating administrative users via the TACACS+ protocol. For additional information, see the TACACS+ Configuration Mode Commands chapter.
Default: normal
Adjusts the IPSec manager task count to support EHA for IKEv1. See task-count below.
Default: normal
increased: Starts additional IPSec manager tasks operating on the packet processing cards. In increased mode, they run on all but demux packet processing cards. Also, all the IPSec managers start at the same time when an active non-demux card is detected and IPSec is configured.
normal: Uses the standard algorithm for allocating memory for IPSec manager tasks. In normal mode, IPSec managers do not run on session packet processing cards.
Caution: If task-count is set to normal and session recovery is enabled, IPSec manager tasks are not allowed to start on most packet processing cards. Because the resources are not reserved, IPSec managers in normal mode only run on demux packet processing cards.Use the following command to set the IPSec manager task count to increased mode:
aggressive: specifies the maximum number of session manager processes are started immediately.
Caution: The task facility sessmgr start aggressive command should only be used if the system will reach capacity (for the existing configuration) during the first few minutes of service.
Caution: This command must only be executed last during configuration (or appended to the end of the configuration file) to ensure the availability of memory resources to contexts and services.normal: indicates the session manager processes are started as needed.
kill: The task most over memory limit (if any) is killed and recovered.
warn: The event is logged and no tasks are killed.
off: Do not use DCD.
on: Use DCD.
Default: 8
7: Use 7 databits to transmit and receive characters.
8: Use 8 databits to transmit and receive characters.
Default: none
hardware: Enables or disables the use of hardware-based flow control
off: Disables the use of Ready to Send (RTS) and Clear to Send (CTS).
on: Enables the use of Ready to Send (RTS) and Clear to Send (CTS).
none: Disables the use of DCD, RTS and CTS.
even - Enables error checking by setting the parity bit to 1 (if needed) making the number of 1s in the data bits even.
none - Disables error checking.
odd - Enables error checking by setting the parity bit to 1 (if needed) making the number of 1s in the data bits odd.
Default: 9600
Default: 1
1: Use one stop bit between each transmitted character.
2: Use two stop bits between each transmitted character.
clear percent
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.Alerts or alarms are triggered for 10-second sample of CPU utilization based on the following rules:
|
•
|
Enter condition: 10-second average percentage of CPU utilization is greater than or equal to the high threshold.
|
|
•
|
Clear condition: 10-second average percentage of CPU utilization is less than the low threshold
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
Important: This command is not supported on all platforms.The following command generates an alert when the 10-second average CPU utilization reaches 45 percent:
Default value for aaa-acct-archive-queue-size1: 25%
Default value for aaa-acct-archive-queue-size2: 50%
Default value for aaa-acct-archive-queue-size3: 90%
clear percent
Default value for aaa-acct-archive-queue-size1: 25%
Default value for aaa-acct-archive-queue-size2: 50%
Default value for aaa-acct-archive-queue-size3: 90%
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual number of archived messages is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual number of archived messages less than the low threshold.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command generates an alarm when 70% of the AAA accounting message archive buffer is filled, and clears the alarm when the buffer size is reduced to 30%:
Specifies the high threshold number of archived accounting messages that must be met or exceeded within the polling interval to generate an alert or alarm. high_thresh is an integer from 0 through 1044000.
clear low_thresh
Specifies the low threshold number of archived accounting messages that maintains a previously generated alarm condition. If the number of failures falls beneath the low threshold within the polling interval, a clear alarm will be generated. low_thresh is an integer from 0 through 1044000.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual number of archived messages that is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual number of archived messages that is less than the low threshold.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a high threshold count of 250 AAA accounting archived messages and low threshold of 100 for a system using the Alarm thresholding model:
Specifies the high threshold number of accounting failures that must be met or exceeded within the polling interval to generate an alert or alarm. high_thresh is an integer from 0 through 10000000. A value of 0 disables the threshold.
clear low_thresh
Specifies the low threshold number of accounting failures that maintains a previously generated alarm condition. If the number of failures falls beneath the low threshold within the polling interval, a clear alarm will be generated. low_thresh is an integer from 0 through 10000000. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual number of failures is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual number of failures is less than the low threshold.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a high threshold count of 100 AAA accounting failures and low threshold of 25 for a system using the Alarm thresholding model:
Specifies the high threshold percent of accounting failures that must be met or exceeded within the polling interval to generate an alert or alarm. high_thresh is an integer from 0 and 100.
clear low_thresh
Specifies the low threshold percent of accounting failures that maintains a previously generated alarm condition. If the percentage of failures falls beneath the low threshold within the polling interval, a clear alarm will be generated. low_thresh is an integer from 0 through 100.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual failure percentage is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual failure percentage is less than the low threshold.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a AAA accounting failure rate high threshold percentage of 30 and a low threshold percentage of 10 for a system using the Alarm thresholding model:
Specifies the high threshold number of authentication failures that must be met or exceeded within the polling interval to generate an alert or alarm.high_thresh is an integer from 0 through 10000000. A value of 0 disables the threshold.
clear low_thresh
Specifies the low threshold number of authentication failures that maintains a previously generated alarm condition. If the number of failures falls beneath the low threshold within the polling interval, a clear alarm will be generated. low_thresh is an integer from 0 through 10000000. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual number of failures is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual number of failures is less than the low threshold.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a high threshold count of 100 AAA authentication failures for a system using the Alert thresholding model:
Specifies the high threshold percent of authentication failures that must be met or exceeded within the polling interval to generate an alert or alarm. high_thresh is an integer from 0 through 100.
Specifies the low threshold percent of authentication failures that maintains a previously generated alarm condition. If the percentage of failures falls beneath the low threshold within the polling interval, a clear alarm will be generated. low_thresh is an integer from 0 through 100.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual failure percentage is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual failure percentage is less than the low threshold
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a AAA authentication failure rate high threshold percentage of 30 for a system using the Alert thresholding model:
Specifies the high threshold percent of AAA request message retries that must be met or exceeded within the polling interval to generate an alert or alarm. high_thresh is an integer from 0 through 100.
clear low_thresh
Specifies the low threshold percent of AAA request message retries that maintains a previously generated alarm condition. If the percentage of retries falls beneath the low threshold within the polling interval, a clear alarm will be generated. low_thresh is an integer from 0 through 100.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual retry percentage is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual retry percentage is less than the low threshold.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a AAA message retry rate high threshold percentage of 25 and a low threshold percentage of 10 for a system using the Alarm thresholding model:
Specifies the high threshold number of AAA Manager Requests that must be met or exceeded within the polling interval to generate an alert or alarm. high_thresh is an integer from 1 through 100.
Specifies the low threshold number of AAA Manager Requests that maintains a previously generated alarm condition. If the percentage of failures falls beneath the low threshold within the polling interval, a clear alarm is generated. low_thresh is an integer from 0 through 100.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual number of AAA Manager Requests per AAA manager is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual number of AAA Manager Requests per AAA manager process is less than the low threshold.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a AAA authentication failure rate high threshold percentage of 30 for a system using the Alert thresholding model:
high_thresh is an integer from 0 through 10000000. A value of 0 disables the threshold.
clear low_thresh
low_thresh is an integer from 0 through 10000000. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual number of failures is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual number of failures is less than the low threshold.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a high threshold count of 100 authentication failures for an ASN-GW using the Alert thresholding model:
high_thresh is an integer from 0 through 10000000. A value of 0 disables the threshold.
clear low_thresh
low_thresh is an integer from 0 through 10000000. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual number of failures is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual number of failures is less than the low threshold.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a high threshold count of 100 hand-off denials using the Alert thresholding model:
high_thresh is an integer from 0 through 10000000. A value of 0 disables the threshold.
clear low_thresh
low_thresh is an integer from 0 through 10000000. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual number of failures is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual number of failures is less than the low threshold.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a high threshold count of 100 alerts or alarms generated on maximum number of retries for EAP authentication for an ASN Gateway using the Alert thresholding model:
high_thresh is an integer from 0 through 10000000. A value of 0 disables the threshold.
clear low_thresh
low_thresh is an integer from 0 through 10000000. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual number of failures is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual number of failures is less than the low threshold.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a high threshold count of 100 network entry denials for an MS using the Alert thresholding model:
high_thresh is an integer from 0 through 10000000. A value of 0 disables the threshold.
clear low_thresh
low_thresh is an integer from 0 through 10000000. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual number of failures is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual number of failures is less than the low threshold.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a high threshold count of 100 invalid NAIs in R6 messages using the Alert thresholding model:
high_thresh is an integer from 0 through 10000000. A value of 0 disables the threshold.
clear low_thresh
low_thresh is an integer from 0 through 10000000. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual number of failures is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual number of failures is less than the low threshold.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a high threshold count of 100 timeouts during session setup using the Alert thresholding model:
high_thresh is an integer from 0 through 10000000. A value of 0 disables the threshold.
clear low_thresh
low_thresh is an integer from 0 through 10000000. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual number of failures is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual number of failures is less than the low threshold.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a high threshold count of 100 timeouts during a session using the Alert thresholding model:
clear low_thresh
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual number of calls rejected due to no resources is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual number of calls rejected due to no resources is less than the low threshold.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a high threshold count for the number of calls rejected by the system due to insufficient or no resources to 100 and allow threshold of 40 for a system using the Alarm thresholding model:
high_thresh is an integer from 0 through 100000. A value of 0 disables the threshold.
clear low_thresh
low_thresh is an integer from 0 through 100000. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual number of call setups is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual number of call setups is less than the low threshold.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
high_thresh is an integer from 0 through 100000. A value of 0 disables the threshold.
clear low_thresh
low_thresh is an integer from 0 through 100000. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual number of call setup failures is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual number of call setup failures is less than the low threshold.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a high threshold count of 100 call setup failures and a low threshold of 80 for a system using the Alarm thresholding model:
low_thresh is measured in megabytes (MB) and is an integer from 0 through 2048.
clear high_thresh
high_thresh is measured in megabytes (MB) and is an integer from 0 through 2048.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the low threshold.|
•
|
Enter condition: Average measured amount of memory/CPU for the last 5 minutes is less than or equal to the low threshold.
|
|
•
|
Clear condition: Average measured amount of memory/CPU for the last 5 minutes is greater than the high threshold.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
Important: This command is not supported on all platforms.The following command configures a low threshold count of 50 MB CPU memory available and a high threshold of 112 MB for a system using the Alarm thresholding model:
If the monitored CPU load is greater than or equal to the specified number an alert is sent. high_thresh must be an integer from 0 through 15.
clear low_thresh
This is a low watermark value that sets the alarm clearing threshold value. If not present it is taken from the first value. low_thresh must be an integer from 0 through 15.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to Specifies the low threshold.|
•
|
Enter condition: Actual CPU load is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual CPU load is less than the low threshold.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
Important: This command is not supported on all platforms.To set an alert when the packet processing card CPU load is over 10 and set an alert clear when the CPU load drops down equal or less than 7, enter the following command;
high_thresh is measured as a percentage of total CPU memory used and is an integer from 0 and 100. A value of 0 disables the threshold.
clear low_thresh
low_thresh is measured as a percentage of total CPU memory used and is an integer from 0 and 100. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to Specifies the low threshold.|
•
|
Enter condition: Actual percentage of CPU memory usage is greater than or equal to the specified percentage of total CPU memory.
|
|
•
|
Clear condition: Actual CPU memory usage is less than the specified clear percentage of total CPU memory usage.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a threshold of 65 percent of total packet processing card CPU memory usage and a clear threshold of 35 percent:
high_thresh is measured in percentage of total CPU utilization and is an integer from 0 through 100. A value of 0 disables the threshold.
clear low_thresh
low_thresh is measured in percentage of total CPU utilization and is an integer from 0 through 100. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to Specifies the low threshold.|
•
|
Enter condition: Actual CPU usage percentage is greater than the high threshold.
|
|
•
|
Clear condition: Actual CPU usage percentage is less than or equal to the low threshold.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a critical-level alarm threshold of 35 percent of CPU utilization by the ORBS task and a clear threshold of 35 percent:
high_thresh is measured in percentage of total CPU utilization and is an integer from 0 through 100. A value of 0 disables the threshold.
clear low_thresh
low_thresh is measured in percentage of total CPU utilization and is an integer from 0 through 100. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to Specifies the low threshold.|
•
|
Enter condition: Actual CPU usage percentage is greater than the high threshold.
|
|
•
|
Clear condition: Actual CPU usage percentage is less than or equal to the low threshold.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a warning-level alarm threshold of 25 percent of CPU utilization by the ORBS task and a clear threshold of 25 percent:
high_thresh is measured in kilobytes per second (Kbps) and is an integer from 0 through 1000000000. A value of 0 disables the threshold.
clear low_thresh
low_thresh is measured in kilobytes per second (Kbps) and is an integer from 0 through 1000000000. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual CPU session throughput is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual CPU session throughput is less than the low threshold.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
Important: This command is not supported on all platforms.The following command configures a high threshold count of 900 Kbps session throughput and a low threshold of 500 KBps for a system using the Alarm thresholding model:
high_thresh is measured in percentage of total allocated CDR file space used and is an integer from 0 through 100. A value of 0 disables the threshold.
clear low_thresh
low_thresh is measured in percentage of total allocated CDR file space used and is an integer from 0 through 100. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to Specifies the low threshold.|
•
|
Enter condition: Actual percentage of allocated CDR file space usage is greater than or equal to the specified percentage of total CDR file space.
|
|
•
|
Clear condition: Actual CDR file space used is less than the specified clear percentage of total allocated CDR file space usage.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a threshold of 65 percent of total allocated CDR file space usage and a clear threshold of 35 percent:
high_thresh is measured in numbers of total rating operations blocked and is an integer from 0 through 1000000. A value of 0 disables the threshold.
clear low_thresh
low_thresh is measured in numbers of total rating operations blocked and is an integer from 0 through 1000000. A value of 0 disables the threshold.
Refer to the threshold poll contfilt-block command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a threshold of 65000 rating operations blocked and a clear threshold of 35000 operations:
high_thresh is measured in numbers of total rating operations performed and is an integer from 0 through 1000000. A value of 0 disables the threshold.
clear low_thresh
low_thresh is measured in umber of total rating operations performed and is an integer from 0 through 1000000. A value of 0 disables the threshold.
Refer to the threshold poll contfilt-rating command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a threshold of 65000 percent of total rating operations performed and a clear threshold of 35000 percent:
high_thresh is an integer from 0 through 100.
clear low_thresh
low_thresh is an integer from 0 through 100.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Average measured CPU utilization for the last 5 minutes
|
|
•
|
Clear condition: Average measured CPU utilization for the last 5 minutes is less than the low threshold.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
Important: This command is not supported on all platforms.The following command configures a high threshold CPU utilization percentage of 90 for a system using the Alert thresholding model:
high_thresh is an integer from 0 through 1000000.
clear low_thresh
low_thresh is an integer from 0 through 1000000.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.In the event that the system receives invalid message or response from Diameter server dcca-bad-answers is generated.
|
•
|
Enter condition: Actual number of DCCA bad answer messages is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual number of DCCA bad answer messages is less than the low threshold.
|
The following command configures a high threshold count of 250 DCCA bad answer messages and low threshold of 100 for a system using the Alarm thresholding model:
high_thresh is an integer from 0 through 1000000.
clear low_thresh
low_thresh is an integer from 0 through 1000000.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.In the event that the system receives the protocol errors from Diameter server, dcca-protocol-error is generated.
|
•
|
Enter condition: Actual number of DCCA protocol error is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual number of DCCA protocol errors is less than the low threshold.
|
The following command configures a high threshold count of 250 protocol errors and low threshold of 100 for a system using the Alarm thresholding model:
high_thresh is an integer from 0 through 1000000.
clear low_thresh
low_thresh is an integer from 0 through 1000000.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.In the event that the Diameter server rejects the system request for a block of credits due to invalid Rating Group, defined as content-id, dcca-rating-failed message is generated.
|
•
|
Enter condition: Actual number of DCCA Rating Group failed is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual number of DCCA Rating Group failed is less than the low threshold.
|
The following command configures a high threshold count of 250 requests rejected and low threshold of 100 for a system using the Alarm thresholding model:
high_thresh is an integer from 0 through 1000000.
clear low_thresh
low_thresh is an integer from 0 through 1000000.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.In the event that the Diameter server sends invalid Rating Groups, content-ids to the system, dcca-unk-rating-group message is generated.
|
•
|
Enter condition: Actual number of unknown rating groups is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual number of unknown rating groups is less than the low threshold.
|
The following command configures a high threshold count of 250 unknown rating groups and low threshold of 100 for a system using the Alarm thresholding model:
Specifies the high threshold. If, within the polling interval, the percentage of Diameter requests retried equals or exceeds high_thresh an alert or alarm is generated.
high_thresh is an integer from 0 through 100.
clear low_thresh
Specifies the low threshold. If, within the polling interval, the percentage of Diameter requests retried falls below low_thresh, a clear alarm is generated.
low_thresh is an integer from 0 through 100.
Important: This value is applicable for the Alarm mode, and ignored for the Alert mode. In addition, if this value is not configured for the Alarm mode, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Percentage of Diameter requests retried is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Percentage of Diameter requests retried is less than the low threshold.
|
The following command configures a high threshold of 75 percent, and a low threshold of 50 percent for a system using the Alarm thresholding model:
high_thresh is an integer value from 0 through 100. When configured to 0 the threshold is disabled.
clear low_thresh
low_thresh is an integer value from 0 through 100. When configured to 0 the threshold is disabled.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the low threshold.|
•
|
Enter condition: Actual percentage of total DNS-learnt IP entries is greater than or equal to the specified percentage of total DNS-learnt IP entries.
|
|
•
|
Clear condition: Actual of total DNS-learnt IP entries is less than the specified clear percentage of total DNS-learnt IP entries.
|
Refer to the threshold poll command to configure the polling interval, and the threshold monitoring ecs command to enable thresholding for this value.
The following command configures a high threshold of 65 percent and a clear threshold of 35 percent for total DNS-learnt IP entries:
high_thresh is measured in percentage of total allocated EDR file space used and is an integer from 0 through 100. A value of 0 disables the threshold.
clear low_thresh
low_thresh is measured in percentage of total allocated EDR file space used and is an integer from 0 through 100. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the low threshold.|
•
|
Enter condition: Actual percentage of allocated EDR file space usage is greater than or equal to the specified percentage of total EDR file space.
|
|
•
|
Clear condition: Actual EDR file space used is less than the specified clear percentage of total allocated EDR file space usage.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a high threshold of 65 percent and a clear threshold of 35 percent for of total allocated EDR file space usage:
high_thresh must be an integer from 0 through 100000.
clear low_thresh
low_thresh must be an integer from 0 through 100000 that must be lower than high_thresh.
|
•
|
Enter condition: Actual number of EDRs + UDRs dropped greater than or equal to the specified number of EDRs + UDRs dropped.
|
|
•
|
Clear condition: Actual number of EDR + UDRs dropped is less than the specified clear number of EDRs + UDRs dropped.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a high threshold of 90 and a clear threshold of 45 to monitor EDRs + UDRs dropped due to flow control:
high_thresh must be an integer from 0 through 1000000.
clear low_thresh
Specifies the Stateful Firewall Deny-Rule alarm clear threshold value. If, in the same polling interval, the threshold falls below low_thresh a clear alarm is generated.
low_thresh must be an integer from 0 through 1000000.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the low threshold.Refer to the threshold poll command to configure the polling interval, and the threshold monitoring command to enable thresholding for this value.
The following command configures a Stateful Firewall Deny Rule high threshold of 1000 and a low threshold of 100 for a system using the Alarm Thresholding model:
high_thresh must be an integer from 0 through 1000000.
clear low_thresh
Specifies the Stateful Firewall DoS attacks clear threshold value. If, in the same polling interval, the threshold falls below low_thresh a clear alarm is generated.
low_thresh must be an integer from 0 through 1000000.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the low threshold.Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a Stateful Firewall DoS attacks high threshold of 1000 and a low threshold of 100 for a system using the Alarm Thresholding model:
high_thresh must be an integer from 0 through 1000000.
clear low_thresh
Specifies the Stateful Firewall drop packets clear threshold value. If, in the same polling interval, the threshold falls below low_thresh a clear alarm is generated.
low_thresh must be an integer from 0 through 1000000.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the low threshold.Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a Stateful Firewall drop packets high threshold of 1000 and a low threshold of 100 for a system using the Alarm thresholding model:
high_thresh must be an integer from 0 through 1000000.
clear low_thresh
Specifies the Stateful Firewall no rules clear threshold value. If, in the same polling interval, the threshold falls below low_thresh a clear alarm is generated.
low_thresh must be an integer from 0 through 1000000.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the low threshold.Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a Stateful Firewall no rules high threshold of 1000 and a low threshold of 100 for a system using the Alarm Thresholding model:
remaining-sessions low_thresh
low_thresh is an integer from 0 through 100.
clear high_thresh
high_thresh is an integer from 0 through 100.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to Specifies the low threshold.|
•
|
Enter condition: Actual session license utilization percentage per session type is greater than or equal to the low threshold.
|
|
•
|
Clear condition: Actual session license utilization percentage per session type is greater than the high threshold.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a session license low threshold percentage of 10 and a high threshold of 35 for a system using the Alarm thresholding model:
high_thresh is measured in percentage of total memory used and can be configured to an integer from 0 through 100. A value of 0 disables the threshold.
clear low_thresh
low_thresh is measured in percentage of total memory used and can be configured to an integer from 0 through 100. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual CPU memory usage is greater than or equal to the high threshold
|
|
•
|
Clear condition: Actual CPU memory usage is less than the low threshold
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
Important: This command is not supported on all platforms.The following command configures a threshold of 65 percent of total SMC CPU memory usage and a clear threshold of 35 percent:
high_thresh is an integer from 0 through 100.
clear low_thresh
low_thresh is an integer from 0 through 100.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Average measured CPU utilization for the last 5 minutes is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Average measured CPU utilization for the last 5 minutes is less than the low threshold.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
Important: This command is not supported on all platforms.The following command configures a high threshold SMC CPU utilization percentage of 90 for a system using the Alert thresholding model:
high_thresh can be configured to an integer from 0 through 100000. A value of 0 disables the threshold.
clear low_thresh
low_thresh is an integer from 0 through 100000. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual total number of MME Attach Failure messages is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual total number of MME Attach Failure messages is less than the low threshold
|
Refer to the threshold poll mme-attach-failure command to configure the polling interval and the threshold monitoring mme-service command to enable thresholding for this value.
The following command configures the limit of MME Attach Failure high threshold count of 10000 for a system using the Alert thresholding model:
high_thresh can be configured to an integer from 0 through 100000. A value of 0 disables the threshold.
clear low_thresh
low_thresh is an integer from 0 through 100000. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual total number of MME Auth Failure messages is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual total number of MME Auth Failure messages is less than the low threshold.
|
Refer to the threshold poll mme-auth-failure command to configure the polling interval and the threshold monitoring mme-service command to enable thresholding for this value.
The following command configures a total MME Auth Failure high threshold count of 10000 for a system using the Alert thresholding model:
Selects the alarm thresholding model as described in the Usage section for this command.
Selects the alert thresholding model as described in the Usage section for this command.
|
•
|
Alert: A value is monitored and an alert condition occurs when the value reaches or exceeds the configured high threshold within the specified polling interval. The alert is generated then generated and/or sent at the end of the polling interval.
|
|
•
|
Alarm: Both high and low threshold are defined for a value. An alarm condition occurs when the value reaches or exceeds the configured high threshold within the specified polling interval. The alert is generated then generated and/or sent at the end of the polling interval.
|
Important: For certain values the alert or alarm serves to warn of low quantities (such as, memory, session licenses, etc.). In these cases, the low threshold is the condition that must be met or exceeded within the polling interval to generate the alert or alarm. When the high threshold is exceeded during an interval, the low quantity condition is cleared.Refer to the threshold monitoring command for additional information on thresholding.
Refer to the threshold aaa-acct-archive-queue-size command for additional information on these values.
Refer to the threshold aaa-acct-failure and threshold aaa-acct-failure-rate commands for additional information on these values.
Refer to the threshold aaa-auth-failure and threshold aaa-auth-failure-rate commands for additional information on these values.
Refer to the threshold aaa-retry-rate command for additional information on this value.
Enables threshold monitoring for AAA Manager Requests for each AAA manager process. Refer to the threshold aaamgr-request-queue command for additional information on these values.
Refer to the threshold call-setup, threshold call-setup-failure, threshold ppp-setup-fail-rate, threshold rp-setup-fail-rate, and threshold call-reject-no-resource commands for additional information on these values.
Refer to the threshold 10sec-cpu-utilization, threshold cpu-available-memory, threshold cpu-load, threshold cpu-memory-usage, threshold cpu-orbs-crit, threshold cpu-orbs-warn, threshold cpu-session-throughput, threshold cpu-utilization, threshold mgmt-cpu-memory-usage, and threshold mgmt-cpu-utilization commands for additional information on these values.
Refer to the threshold cpu-session-throughput command for additional information on this value.
Refer to the threshold reg-reply-error FA Service Configuration Mode command for additional information on this value.
Refer to the threshold fw-deny-rule, threshold fw-dos-attack, threshold fw-drop-packet, and threshold fw-no-rule commands for additional information on this value.
Important: Stateful Firewall thresholds can only be enabled if the Stateful Firewall license is present.Refer to the threshold init-rrq-rcvd-rate, threshold reg-reply-error, threshold rereg-reply-error, and threshold dereg-reply-error HA Service Configuration Mode commands and the threshold ha-service init-rrq-rcvd-rate Context Configuration mode command for additional information on this value.
Important: This keyword is required to activate the threshold alarm/alert for HNB-GW service to use threshold total-hnbgw-hnb-sessions, thresshold total-hnbgw-iu-sessions, and thresshold total-hnbgw-ue-sessions command for threshold values.Refer to the threshold license command for additional information on this value.
Refer to the threshold total-mme-sessions commands for additional information on this value.
Refer to the threshold packets-filtered-dropped command for additional information on this value.
Refer to the threshold packets-forwarded-to-cpu command for additional information on this value.
Refer to the threshold packets-forwarded-to-cpu command for additional information on this value.
Refer to the ip maximum-routes command in Context configuration mode and threshold route-service bgp-routes in this mode for more information on route thresholds.
Refer to the threshold subscriber active, threshold subscriber total, threshold total-ggsn-sessions, threshold total-gprs-sessions, threshold total-gprs-pdp-sessions, threshold total-ha-sessions, threshold total-lns-sessions, threshold total-pdsn-sessions, threshold total-sgsn-sessions, threshold total-sgsn-pdp-sessions, threshold per-service-ggsn-sessions, threshold per-service-ha-sessions, threshold per-service-lns-sessions, and threshold per-service-pdsn-sessions commands for additional information on these values.
|
•
|
SNMP traps: SNMP traps have been created that indicate the condition (high threshold crossing and/or clear) of each of the monitored values. Complete descriptions and other information pertaining to these traps is located in the starentMIB(8164).starentTraps(2) section of the SNMP MIB Reference.
|
|
•
|
Logs: The system provides a facility called threshold for which active and event logs can be generated. As with other system facilities, logs are generated Log messages pertaining to the condition of a monitored value are generated with a severity level of WARNING.
|
|
•
|
Alarm System: High threshold alarms generated within the specified polling interval are considered “outstanding” until a the condition no longer exists and/or a condition clear alarm is generated.
|
In addition to the values that can be enabled by this command, the system supports the enabling of threshold monitoring for IP pool address availability (refer to the ip pool and threshold commands in this reference) and port utilization (refer to the threshold commands in this chapter).
Important: This command is only available in 8.3 and later releases.high_thresh must be an integer from 0 through 100. A value of 0 disables the threshold.
clear low_thresh
low_thresh must be an integer from 0 through 100. A value of 0 disables the threshold. If not set, the high_thresh will be the high and low threshold setting.
The following command sets the NAT port chunk utilization threshold settings to a high of 75% and a low of 15%:
high_thresh is an integer from 0 through 1000000000. A value of 0 disables the threshold.
clear low_thresh
low_thresh is an integer from 0 through 1000000000. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual number of filtered/dropped packets is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual number of filtered/dropped packets is less than the low threshold.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value. In addition, refer to information on ACLs in this reference.
The following command configures a filtered/dropped packet high threshold count of 150000 for a system using the Alert thresholding model:
high_thresh is an integer from 0 through 1000000000. A value of 0 disables the threshold.
clear low_thresh
low_thresh is an integer from 0 through 1000000000. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.
Important: Ping and/or traceroute packets are intentionally forwarded to system CPUs for processing. These packet types are included in the packet count for this threshold.|
•
|
Enter condition: Actual number of forwarded packets is greater than or equal to the high threshold
|
|
•
|
Clear condition: Actual number of forwarded packets is less than the low threshold.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a forwarded packet high threshold count of 10000 for a system using the Alert thresholding model:
Configures the total number of active PDG sessions to be monitored on a chassis. high_thresh is an integer from 0 through 300000.
clear low_thresh
Clears the number of sessions being monitored using the high_thresh variable defined above.
low_thresh is an integer from 0 through 100000.
The following command configures a monitoring threshold of 300000 active PDG sessions on a chassis:
Configures the total number of PDG sessions on a chassis, both active and inactive. high_thresh is any integer from 0 through 300000.
clear low_thresh
Clears any number of sessions being monitored using the high_thresh variable defined above.
low_thresh is any integer from 0 through 100000.
The following command configures a monitoring threshold of 300000 active and inactive PDG sessions on a chassis:
Configures the total number of PDIF sessions on a chassis, both active and inactive. high_thresh is an integer from 0 through 1000000.
clear low_thresh
Clears the specified number of sessions being monitored using the high_thresh variable defined above. low_thresh is an integer from 0 through 1000000.
The following command configures a monitoring threshold of 300000 active and inactive PDIF sessions on a chassis:
Configures the total number of active PDIF sessions to be monitored on a chassis. high_thresh is any integer from 0 through 1000000.
clear low_thresh
Clears the specified number of sessions being monitored using the high_thresh variable defined above. low_thresh is any integer from 0 through 1000000.
The following command configures a monitoring threshold of 300000 active PDIF sessions on a chassis:
high_thresh is an integer from 0 through 4000000. A value of 0 disables the threshold.
clear low_thresh
low_thresh is an integer from 0 through 4000000. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual number of PDP contexts for any GGSN service is greater than or equal to the high threshold
|
|
•
|
Clear condition: Actual number of PDP contexts is less than the low threshold
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a high threshold count of 10000 subscriber attaches per GGSN service for the Alert thresholding model:
high_thresh is an integer from 0 through 4000000. A value of 0 disables the threshold.
clear low_thresh
low_thresh is an integer from 0 through 4000000. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual number of PDP contexts for any GPRS service is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual number of PDP contexts is less than the low threshold.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a high threshold count of 10000 2G-activated PDP contexts per GPRS service for the Alert thresholding model:
high_thresh is an integer from 0 through 2000000. A value of 0 disables the threshold.
clear low_thresh
low_thresh is an integer from 0 through 2000000. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual number of 2G-attached subscribers for any GPRS service is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual number of 2G-attached subscribers is less than the low threshold.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a high threshold count of 10000 2G-attaches per GPRS service for the Alert thresholding model:
high_thresh is an integer from 0 through 500000. A value of 0 disables the threshold.
clear low_thresh
low_thresh is an integer from 0 through 500000. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual number of HA sessions for any HA service is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual number of HA sessions is less than the low threshold.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a HA session per service high threshold count of 10000 for a system using the Alert thresholding model:
high_thresh is an integer from 0 through 500000. A value of 0 disables the threshold.
clear low_thresh
low_thresh is an integer from 0 through 500000. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual number of LNS sessions for any LNS service is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual number of LNS sessions is less than the low threshold.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a LNS session per service high threshold count of 10000 for a system using the Alert thresholding model:
high_thresh is an integer from 0 through 500000. A value of 0 disables the threshold.
clear low_thresh
low_thresh is an integer from 0 through 500000. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual number of PDSN sessions for any PDSN service is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual number of PDSN sessions is less than the low threshold.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a HA session per service high threshold count of 10000 for a system using the Alert thresholding model:
high_thresh is an integer from 0 through 4000000. A value of 0 disables the threshold.
clear low_thresh
low_thresh is an integer from 0 through 2400000. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual number of 3G-activated PDP contexts for any SGSN service is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual number of 3G-activated PDP contexts is less than the low threshold
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a high threshold count of 10000 3G-activated PDP contexts per SGSN service for the system’s Alert thresholding model:
high_thresh is an integer from 0 through 2000000. A value of 0 disables the threshold.
clear low_thresh
low_thresh is an integer from 0 through 2000000. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual number of 3G-attached subscribers for any single SGSN service is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual number of 3G-attached subscribers for any single SGSN service is less than the low threshold.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a high threshold count of 10000 3G-attached subscribers per SGSN service for a system using the Alert thresholding model:
[ default ] threshold poll { 10sec-cpu-utilization | all-ppp-send-discard | a11-rac-msg-discard |a11-rrp-failure | a11-rrq-msg-discard | aaa-acct-archive-queue-size1 | aaa-acct-archive-queue-size2 | aaa-acct-archive-queue-size3 aaa-acct-archive-size | aaa-acct-failure | aaa-acct-failure-rate | aaa-auth-failure | aaa-auth-failure-rate | aaa-retry-rate | aaamgr-request-queue | active-subscriber | asngw-auth-failure | asngw-handoff-denial | asngw-max-eap-retry | asngw-network-entry-denial | asngw-session-setup-timeout | asngw-session-timeout | asnpc-idle-mode-timeout | asnpc-im-entry-denial | asnpc-lu-denial | asnpc-session-setup-timeout | available-ip-pool-group | call-reject-no-resource | call-setup | call-setup-failure | call-setup-failures | call-total-active | cdr-file-space | contfilt-block | contfilt-rating | cpu-available-memory | cpu-load | cpu-memory-usage | cpu-orbs-crit | cpu-orbs-warn | cpu-session-throughput | cpu-utilization | cscf-invite-rcvd | cscf-reg-rcvd | cscf-service-route-failures | dcca-bad-answers | dcca-protocol-error | dcca-rating-failed | dcca-unknown-rating-group | dereg-reply-error | | diameter-retry-rate | edr-file-space | edr-udr-dropped-flow-control | error-no-resource| error-presence | error-reg-auth | error-tcp| fa-reg-reply-error | fng-current-active-sessions | fng-current-sessions | fw-deny-rule | fw-dos-attack | fw-drop-packet | fw-no-rule | ha-init-rrq-rcvd-rate | ha-svc-init-rrq-rcvd-rate | ip-pool-free | ip-pool-hold | ip-pool-release | ip-pool-used | ipsec-call-req-rej | ipsec-ike-failrate | ipsec-ike-failures | ipsec-ike-requests | ipsec-tunnels-established | ipsec-tunnels-setup | license-remaining-session | mgmt-cpu-memory-usage interval | mgmt-cpu-utilization | nat-port-chunks-usage | packets-filtered-dropped | packets-forwarded-to-cpu | pdg-current-active-sessions | pdg-current-sessions | pdif-current-active-sessions | pdif-current-sessions | pdsn-init-rrq-rcvd-rate | pdsn-svc-init-rrq-rcvd-rate | per-service-asngw-sessions | per-service-ggsn-sessions | per-service-gprs-sessions | per-service-gprs-pdp-sessions | per-service-ha-sessions | per-service-lns-sessions | per-service-pdsn-sessions | per-service-sgsn-sessions | per-service-sgsn-pdp-sessions | port-high-activity | port-rx-utilization | port-tx-utilization | ppp-setup-fail-rate | reg-reply-error | reg-total-active | rereg-reply-error | route-service | rp-setup-fail-rate | storage-utilization total-asngw-sessions | total-ggsn-sessions | total-gprs-sessions | total-gprs-pdp sessions | total-ha-sessions | total-hsgw-sessions | total-lma-sessions | total-lns-sessions | total-mme-sessions | total-pdsn-sessions | total-pgw-sessions | total-sgsn-sessions | total-sgsn-pdp-sessions | total-sgw-sessions | total-subscriber } interval time
Important: When specifying interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)Configures the polling interval over which to count A11 Registration Response failures. When specifying interval time for this threshold, the range is from 60 through 900 seconds.
Configures the polling interval over which to count how many A11 Registration Request messages are discarded. When specifying interval time for this threshold, the range is from 60 through 900 seconds.
Configures the polling interval over which to count how many A11 Registration Acknowledgement messages are discarded. When specifying interval time for this threshold, the range is from 60 through 900 seconds.
Configures the polling interval over which to measure the percentage of AAA authentication failures.
Configures the polling interval over which to count the number of AAA Manager Requests for each AAA manager process. When specifying interval time for this threshold, the range is from 60 through 60000 seconds.
Configures the polling interval over which to count the number of discarded PPP send packets. When specifying interval time for this threshold, the range is from 60 through 900 seconds.
Important: When specifying interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)time must an integer value from 60 to 60000 and expressed in multiples of 30. The system will round up all other configured values to a multiple of 30.
time must an integer value from 60 to 60000 and expressed in multiples of 30. The system will round up all other configured values to a multiple of 30.
Important: When specifying interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: This command is not supported on all platforms
Important: When specifying interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: This command is not supported on all platforms
Important: When specifying interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: This command is not supported on all platformsConfigures the polling interval over which to measure packet processing card CPU session throughput.
Important: This command is not supported on all platforms
Important: When specifying interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: This command is not supported on all platformstime must an integer value from 60 to 60000 and expressed in multiples of 30. The system will round up all other configured values to a multiple of 30.
time must an integer value from 60 to 60000 and expressed in multiples of 30. The system will round up all other configured values to a multiple of 30.
time must an integer value from 60 to 60000 and expressed in multiples of 30. The system will round up all other configured values to a multiple of 30.
Configures the polling interval in seconds over which to count Diameter unknown rating group errors.
Configures the polling interval over which to measure the number of de-registration reply errors for HA services. When specifying interval time for this threshold, the range is from 60 through 900 seconds.
Configures the polling interval over which to measure the number of retries to Diameter server. When specifying interval time for this threshold, the range is from 60 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30.
time must an integer value from 60 to 60000 and expressed in multiples of 30. The system will round up all other configured values to a multiple of 30.
time must an integer value from 60 to 60000 and expressed in multiples of 30. The system will round up all other configured values to a multiple of 30.
time must an integer value from 60 to 60000 and expressed in multiples of 30. The system will round up all other configured values to a multiple of 30.
time must an integer value from 60 to 60000 and expressed in multiples of 30. The system will round up all other configured values to a multiple of 30.
Configures the polling interval over which to measure the number of registration reply errors for FA services. When specifying interval time for this threshold, the range is from 60 through 900 seconds.
Configures the polling interval over which to measure the average number of calls setup per minute for the context. When specifying interval time for this threshold, the range is from 60 through 900 seconds.
Configures the polling interval over which to measure the average number of calls setup per minute for HA services. When specifying interval time for this threshold, the range is from 60 through 900 seconds.
Important: When specifying interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: When specifying interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: When specifying interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: When specifying interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: When specifying interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: This command is not supported on all platforms
Important: When specifying interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: This command is not supported on all platforms.
Important: This keyword is only available in 8.3 and later releases.Configures the polling interval for all current PDIF sessions in seconds rounded to the nearest multiple of 30 seconds. period is an integer from 30 to 60000.
Configures the polling interval for active sessions only in seconds rounded to the nearest multiple of 30 seconds. period is an integer from 30 to 60000.
Configures the polling interval over which to measure the average number of calls setup per second for a PDSN-service. When specifying interval time for this threshold, the range is from 60 through 900 seconds.
Important: When specifying interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: When specifying interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: When specifying interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: When specifying interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: When specifying interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: When specifying interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: When specifying interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: When specifying interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: This command is not supported on all platforms
Important: This command is not supported on all platforms
Important: This command is not supported on all platformsConfigures the polling interval over which to measure number of registration reply errors for HA services. When specifying interval time for this threshold, the range is from 60 through 900 seconds.
time must an integer value from 60 to 60000 and expressed in multiples of 30. The system will round up all other configured values to a multiple of 30.
Configures the polling interval over which to measure number of re-registration reply errors for HA services. When specifying interval time for this threshold, the range is from 60 through 900 seconds.
Important: This command has been renamed to threshold mgmt-cpu-memory-usage. Please refer to that command for details. Note that for backwards compatibility, the system accepts this command as valid.
Important: This command is not supported on all platforms
Important: This command has been renamed to threshold mgmt-cpu-utilization. Please refer to that command for details. Note that for backwards compatibility, the system accepts this command as valid.
Important: This command is not supported on all platformsConfigures the polling interval over which to count the total number of GGSN sessions on the system.
Important: When specifying interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: When specifying interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: When specifying interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: When specifying interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)Configures the polling interval over which to count the total number of HSGW sessions on the system.
Important: When specifying interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: When specifying interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: When specifying interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)Configures the polling interval over which to count the total number of PDSN sessions on the system.
Important: When specifying interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)Configures the polling interval over which to count the total number of P-GW sessions on the system.
Important: When specifying interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)Configures the polling interval over which to count the total number of SGSN sessions on the system.
Important: When specifying interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)Configures the polling interval over which to count the total number of SGSN sessions on the system.
Important: When specifying interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)Configures the polling interval over which to count the total number of S-GW sessions on the system.
Important: When specifying interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)interval time
time is measured in seconds and can be configured to any integer value from 60 to 60000 unless otherwise noted in keyword descriptions.
Important: All configured polling intervals are rounded up to the closest multiple of 30. For example, if a polling interval is configured for 130 seconds, the system uses a polling interval of 150 seconds.Refer to the threshold model and threshold monitoring commands for additional information on the system’s support for thresholding.
The following command configures the polling interval for the total subscribers threshold value to 600 seconds (10 minutes):
interval duration
duration is an integer from 60 through 60000 in multiples of 30.
Important: All configured polling intervals are rounded up to the closest multiple of 30. For example, if a polling interval is configured for 130 seconds, the system uses a polling interval of 150 seconds.Refer to the threshold monitoring and other threshold commands for additional information on the system’s support for thresholds in this chapter.
The following command configures the polling interval to 600 seconds for the AAA accounting archive queue size threshold:
interval duration
duration is an integer from 60 through 60000 in multiples of 30.
Important: All configured polling intervals are rounded up to the closest multiple of 30. For example, if a polling interval is configured for 130 seconds, the system uses a polling interval of 150 seconds.Refer to the threshold monitoring and other threshold commands for additional information on the system’s support for thresholds in this chapter.
The following command configures the polling interval to 600 seconds for the AAA accounting archive size threshold:
interval duration
duration is an integer from 60 through 60000 in multiples of 30.
Important: All configured polling intervals are rounded up to the closest multiple of 30. For example, if a polling interval is configured for 130 seconds, the system uses a polling interval of 150 seconds.Refer to the threshold monitoring and other threshold commands for additional information on the system’s support for thresholds in this chapter.
The following command configures the polling interval to 600 seconds for the AAA accounting failure threshold:
interval duration
duration is an integer from 60 through 60000 in multiples of 30.
Important: All configured polling intervals are rounded up to the closest multiple of 30. For example, if a polling interval is configured for 130 seconds, the system uses a polling interval of 150 seconds.Refer to the threshold monitoring and other threshold commands for additional information on the system’s support for thresholds in this chapter.
The following command configures the polling interval to 600 seconds for the AAA accounting failure rate threshold:
interval duration
duration is an integer from 60 through 60000 in multiples of 30.
Important: All configured polling intervals are rounded up to the closest multiple of 30. For example, if a polling interval is configured for 130 seconds, the system uses a polling interval of 150 seconds.Refer to the threshold monitoring and other threshold commands for additional information on the system’s support for thresholds in this chapter.
The following command configures the polling interval to 600 seconds for the AAA authentication failure threshold:
Configures the polling interval over which to measure the percentage of AAA authentication failures.
interval duration
duration is an integer from 60 through 60000 in multiples of 30.
Important: All configured polling intervals are rounded up to the closest multiple of 30. For example, if a polling interval is configured for 130 seconds, the system uses a polling interval of 150 seconds.Refer to the threshold monitoring and other threshold commands for additional information on the system’s support for thresholds in this chapter.
The following command configures the polling interval to 600 seconds for the AAA authentication failure rate threshold:
interval duration
duration is an integer from 60 through 60000 in multiples of 30.
Important: All configured polling intervals are rounded up to the closest multiple of 30. For example, if a polling interval is configured for 130 seconds, the system uses a polling interval of 150 seconds.Refer to the threshold monitoring and other threshold commands for additional information on the system’s support for thresholds in this chapter.
The following command configures the polling interval to 600 seconds for the AAA retry rate threshold:
interval duration
duration is an integer from 60 through 60000 in multiples of 30.
Important: All configured polling intervals are rounded up to the closest multiple of 30. For example, if a polling interval is configured for 130 seconds, the system uses a polling interval of 150 seconds.Refer to the threshold monitoring and other threshold commands for additional information on the system’s support for thresholds in this chapter.
The following command configures the polling interval to 600 seconds for the AAA manager request queue threshold:
interval dur
dur is an integer from 30 through 60000 in multiples of 30.
Important: All configured polling intervals are rounded up to the closest multiple of 30. For example, if a polling interval is configured for 130 seconds, the system uses a polling interval of 150 seconds.Refer to the threshold monitoring and other threshold commands for additional information on the system’s support for thresholds in this chapter.
The following command configures the polling interval to 600 seconds for the ASN Gateway authentication failure threshold:
interval dur
dur is an integer from 30 through 60000 in multiples of 30.
Important: All configured polling intervals are rounded up to the closest multiple of 30. For example, if a polling interval is configured for 130 seconds, the system uses a polling interval of 150 seconds.Refer to the threshold monitoring and other threshold commands for additional information on the system’s support for thresholds in this chapter.
The following command configures the polling interval to 600 seconds for hand-off denial threshold:
interval dur
dur is an integer from 30 through 60000 in multiples of 30.
Important: All configured polling intervals are rounded up to the closest multiple of 30. For example, if a polling interval is configured for 130 seconds, the system uses a polling interval of 150 seconds.Refer to the threshold monitoring and other threshold commands for additional information on the system’s support for thresholds in this chapter.
The following command configures the polling interval to 600 seconds for maximum EAP authentication retry threshold:
interval dur
dur is an integer from 30 through 60000 in multiples of 30.
Important: All configured polling intervals are rounded up to the closest multiple of 30. For example, if a polling interval is configured for 130 seconds, the system uses a polling interval of 150 seconds.Refer to the threshold monitoring and other threshold commands for additional information on the system’s support for thresholds in this chapter.
The following command configures the polling interval to 600 seconds for network entry denial threshold:
interval dur
dur is an integer from 30 through 60000 in multiples of 30.
Important: All configured polling intervals are rounded up to the closest multiple of 30. For example, if a polling interval is configured for 130 seconds, the system uses a polling interval of 150 seconds.Refer to the threshold monitoring and other threshold commands for additional information on the system’s support for thresholds in this chapter.
The following command configures the polling interval to 600 seconds for invalid NAIs in R6 messages threshold:
interval dur
dur is an integer from 30 through 60000 in multiples of 30.
Important: All configured polling intervals are rounded up to the closest multiple of 30. For example, if a polling interval is configured for 130 seconds, the system uses a polling interval of 150 seconds.Refer to the threshold monitoring and other threshold commands for additional information on the system’s support for thresholds in this chapter.
The following command configures the polling interval to 600 seconds for session setup timeout threshold:
interval dur
dur is an integer from 30 through 60000 in multiples of 30.
Important: All configured polling intervals are rounded up to the closest multiple of 30. For example, if a polling interval is configured for 130 seconds, the system uses a polling interval of 150 seconds.Refer to the threshold monitoring and other threshold commands for additional information on the system’s support for thresholds in this chapter.
The following command configures the polling interval to 600 seconds for session timeout threshold:
interval duration
duration must be an integer from 60 through 60000.
Important: All configured polling intervals are rounded up to the closest multiple of 30. For example, if a polling interval is configured for 130 seconds, the system uses a polling interval of 150 seconds.Refer to the threshold monitoring and other threshold commands for additional information on the system’s support for thresholds in this chapter.
The following command configures the polling interval to 600 seconds for the CDR file space usage threshold:
interval duration
duration must be an integer from 60 through 60000.
Important: All configured polling intervals are rounded up to the closest multiple of 30. For example, if a polling interval is configured for 130 seconds, the system uses a polling interval of 150 seconds.Refer to the threshold monitoring and other threshold commands for additional information on the system’s support for thresholds in this chapter.
The following command configures the polling interval to 600 seconds for the content filtering blocking threshold:
interval dur
duration must be an integer from 60 through 60000.
Important: All configured polling intervals are rounded up to the closest multiple of 30. For example, if a polling interval is configured for 130 seconds, the system uses a polling interval of 150 seconds.Refer to the threshold monitoring and other threshold commands for additional information on the system’s support for thresholds in this chapter.
The following command configures the polling interval to 600 seconds for the content filtering rating processing threshold:
interval duration
duration must be an integer from 60 through 60000.
Important: All configured polling intervals are rounded up to the closest multiple of 30. For example, if a polling interval is configured for 130 seconds, the system uses a polling interval of 150 seconds.Refer to the threshold monitoring and other threshold commands for additional information on the system’s support for thresholding in this chapter.
The following command configures the polling interval to 600 seconds for invalid or bad response threshold to the system from Diameter server:
interval duration
duration must be an integer from 60 through 60000.
Important: All configured polling intervals are rounded up to the closest multiple of 30. For example, if a polling interval is configured for 130 seconds, the system uses a polling interval of 150 seconds.Refer to the threshold monitoring and other threshold commands for additional information on the system’s support for thresholding in this chapter.
The following command configures the polling interval to 600 seconds for the DCCA protocol error threshold:
interval duration
duration must be an integer from 60 through 60000.
Important: All configured polling intervals are rounded up to the closest multiple of 30. For example, if a polling interval is configured for 130 seconds, the system uses a polling interval of 150 seconds.Refer to the threshold monitoring and other threshold commands for additional information on the system’s support for thresholding in this chapter.
The following command configures the polling interval to 600 seconds for the Diameter Credit Control Application (DCCA) Rating Group (content-id) request reject thresholds:
interval duration
duration must be an integer from 60 through 60000.
Important: All configured polling intervals are rounded up to the closest multiple of 30. For example, if a polling interval is configured for 130 seconds, the system uses a polling interval of 150 seconds.Refer to the threshold monitoring and other threshold commands for additional information on the system’s support for thresholding in this chapter.
The following command configures the polling interval to 600 seconds to threshold for the unknown DCCA Rating Group (content-id) returned by Diameter to system:
interval duration
duration must be an integer from 60 through 60000. The input will be rounded up to the closest multiple of 30.
Important: All configured polling intervals are rounded up to the closest multiple of 30. For example, if a polling interval is configured for 130 seconds, the system uses a polling interval of 150 seconds.Refer to the threshold monitoring and other threshold commands in this chapter for additional information on the system’s support for thresholding.
This command configures the polling interval for Event Data Record (EDR) File Space Usage threshold.
interval duration
duration must be an integer from 60 through 60000.
Important: All configured polling intervals are rounded up to the closest multiple of 30. For example, if a polling interval is configured for 130 seconds, the system uses a polling interval of 150 seconds.Refer to the threshold monitoring ecs and other threshold commands for additional information on the system’s support for thresholds in this chapter.
The following command configures the polling interval to 600 seconds for the EDR file space usage threshold:
interval dur
dur must be an integer from 30 through 60000 in multiples of 30.
Important: All configured polling intervals are rounded up to the closest multiple of 30. For example, if a polling interval is configured for 130 seconds, the system uses a polling interval of 150 seconds.Refer to the threshold monitoring mme-service and other threshold commands for additional information on the system’s support for thresholds in this chapter.
The following command configures the polling interval of 600 seconds to count the MME Attach Failure messages for threshold limit:
interval dur
dur must be an integer from 30 through 60000 in multiples of 30.
Important: All configured polling intervals are rounded up to the closest multiple of 30. For example, if a polling interval is configured for 130 seconds, the system uses a polling interval of 150 seconds.Refer to the threshold monitoring mme-service and other threshold commands for additional information on the system’s support for thresholds in this chapter.
The following command configures the polling interval of 600 seconds to count the MME Auth Failure messages for threshold limit:
interval time
time must be an integer from 30 through 60000.
Important: All configured polling intervals are rounded up to the closest multiple of 30. For example, if a polling interval is configured for 130 seconds, the system uses a polling interval of 150 seconds.Refer to the threshold model and threshold monitoring commands for additional information on the system’s support for thresholding.
Important: To enable SNMP trap for threshold monitoring of this threshold use snmp trap enable ThreshTotalHNBGWHnbSess command in this mode.The following command configures the polling interval for counting the total number of IuH sessions between HNB and HNB-GW across all the HNB-GW services on a system, to 600 seconds (10 minutes):
interval time
time must be an value from 30 through 60000.
Important: All configured polling intervals are rounded up to the closest multiple of 30. For example, if a polling interval is configured for 130 seconds, the system uses a polling interval of 150 seconds.Refer to the threshold model and threshold monitoring commands for additional information on the system’s support for thresholding.
Important: To enable SNMP trap for threshold monitoring to this threshold use snmp trap enable ThreshTotalHNBGWIuSess command in this mode.The following command configures the polling interval for counting the total number of subscriber sessions across all the HNB-GW services on a system, to 600 seconds (10 minutes):
interval time
time must be an integer from 30 through 60000.
Important: All configured polling intervals are rounded up to the closest multiple of 30. For example, if a polling interval is configured for 130 seconds, the system uses a polling interval of 150 seconds.Refer to the threshold model and threshold monitoring commands for additional information on the system’s support for thresholding.
Important: To enable SNMP trap for threshold monitoring to this threshold use snmp trap enable ThreshTotalHNBGWUeSess command in this mode.The following command configures the polling interval for the total number of UEs connected to an HNB-GW service across all the HNB-GW services on a system, to 600 seconds (10 minutes):
interval time
time must be an ny integer from 30 through 60000.
Important: All configured polling intervals are rounded up to the closest multiple of 30. For example, if a polling interval is configured for 130 seconds, the system uses a polling interval of 150 seconds.Refer to the threshold model and threshold monitoring commands for additional information on the system’s support for thresholding.
The following command configures the polling interval for the total MME session threshold polling duration value to 600 seconds (10 minutes):
interval seconds
Configures the threshold polling interval in multiples of 30 seconds. seconds is an integer from 30 to 60000
Receive port utilization thresholds generate alerts or alarms based on the utilization percentage of each configured port in relation to data received during the specified polling interval. This threshold is configured on a per-port basis configured using the port port-type slot#/port# command syntax.
Important: This command is not available on all platforms
Important: Ports configured for half-duplex do not differentiate between data received and data transmitted. (The transmitted and received percentages are combined.) Therefore, to avoid redundant alarms, it is recommended that only the receive or transmit utilization threshold be configured.Use the following example to configure a threshold poll interval of 300 seconds (5 minutes)
interval seconds
Configures the threshold polling interval in multiples of 30 seconds. seconds is an integer from 30 through 60000
Transmit port utilization thresholds generate alerts or alarms based on the utilization percentage of each configured port in relation to data transmitted during the specified polling interval. This threshold is configured on a per-port basis configured using the port port-type slot#/port# command syntax.
Important: This command is not available on all platforms
Important: Ports configured for half-duplex do not differentiate between data received and data transmitted. (The transmitted and received percentages are combined.) Therefore, to avoid redundant alarms, it is recommended that only the receive or transmit utilization threshold be configured.Use the following example to configure a threshold poll interval of 300 seconds (5 minutes)
interval seconds
Configures the threshold polling interval in multiples of 30 seconds. seconds is an integer from 30 through 60000
If a trigger condition occurs within the polling interval, the alert or alarm will not be generated until the end of the polling interval.This threshold is configured on a per-port basis configured using the port port-type slot#/port# command syntax.
Important: This command is not available on all platformsUse the following example to configure the polling interval over which to measure for high port activity to 300 seconds:
interval time
dur is any integer from 30 through 60000.
Important: All configured polling intervals are rounded up to the closest multiple of 30. For example, if a polling interval is configured for 130 seconds, the system uses a polling interval of 150 seconds.Refer to the threshold model and threshold monitoring commands for additional information on the system’s support for thresholding.
The following command configures the polling interval for the total BGP routes threshold polling duration value to 600 seconds (10 minutes):
interval must be an integer from 30 through 60000. The system rounds up the value to the closest multiple of 30.
The following command configures the polling interval for TPO DNS resolution failures threshold to 600 seconds:
interval must be an integer from 30 through 60000. The system rounds up the value to the closest multiple of 30.
The following command configures the polling interval for TPO low-compression-gain results threshold to 600 seconds:
interval must be an integer from 30 through 60000. The system rounds up the value to the closest multiple of 30.
The following command configures the polling interval for TPO retransmission timeouts threshold to 600 seconds:
high_thresh is an integer from 0 through 100. A value of 0 disables the threshold.
clear low_thresh
low_thresh is an integer from 0 through 100. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual number of call setup failures is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual number of call setup failures is less than the low threshold.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a PPP setup failure rate high percentage threshold of 50 percent and a clear threshold of 45 percent:
high_thresh is an integer from 0 through 100. A value of 0 disables the threshold.
clear low_thresh
low_thresh is an integer from 0 through 100. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.Use this command to configure a threshold in percentage of maximum BGP routes allowed. If the percentage of the number of BGP routes in a context (including all VRFs) reaches high_thresh, a notification is generated. Optionally, if the threshold subsystem is configured in ‘alarm’ mode, a Threshold_Clear notification is generated when the percentage of the number of BGP routes in a context (including all VRFs) goes below low_thresh. The maximum number of BGP routes is also sent by BGP task when getting the stats
|
•
|
Enter condition: Actual number of call setup failures is greater than the high threshold.
|
|
•
|
Clear condition: Actual number of call setup failures is less than the low threshold.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures system for high threshold of 50 percent and a clear threshold of 45 percent:
high_thresh is an integer from 0 through 100. A value of 0 disables the threshold.
clear low_thresh
low_thresh is an integer from 0 through 100. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual number of call setup failures is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual number of call setup failures is less than the low threshold.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a RP setup failure rate high threshold of 50 percent and a clear threshold of 45 percent:
This command has been renamed to threshold mgmt-cpu-memory-usage. Please refer to that command for details. Note that for backwards compatibility, the system accepts this command as valid.
Important: This command is not supported on all platforms.This command has been renamed to threshold mgmt-cpu-utilization. Please refer to that command for details. Note that for backwards compatibility, the system accepts this command as valid.
high_thresh is an integer from 0 through 100. A value of 0 disables the threshold.
clear low_thresh
low_thresh is an integer from 0 through 100. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual percentage memory utilization is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual percentage memory utilization is less than the low threshold.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a high threshold flash utilization percentage of 85 for a system using the Alert thresholding model:
high_thresh is an integer from 0 through 4000000. A value of 0 disables the threshold.
clear low_thresh
low_thresh is an integer from 0 and 4000000. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual total number of active subscriber sessions is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual total number of active subscriber sessions is less than the low threshold.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures an active subscriber high threshold count of 150000 and a low threshold of 100000 for a system using the Alarm thresholding model:
high_thresh is an integer from 0 through 4000000. A value of 0 disables the threshold.
clear low_thresh
low_thresh is an integer from 0 and 4000000. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual total number of subscriber sessions is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual total number of subscriber sessions is less than the low threshold.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures an active subscriber high threshold count of 450000 and a low threshold of 250000 for a system using the Alarm thresholding model:
high_thresh is an integer from 0 through 4000000. A value of 0 disables the threshold.
clear low_thresh
low_thresh is an integer from 0 and 4000000. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual total number of GGSN sessions is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual total number of GGSN sessions is less than the low threshold.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a total GGSN session high threshold count of 10000 for a system using the Alert thresholding model:
high_thresh is an integer from 1 through 2000000. A value of 0 disables the threshold.
clear low_thresh
low_thresh is an integer from 0 and 2000000. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual total number of GPRS sessions is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual total number of GPRS sessions is less than the low threshol.d
|
Refer to the command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a total number of GPRS sessions high threshold count of 10000 for a system using the Alert thresholding model:
high_thresh is an integer from 1 through 2000000. A value of 0 disables the threshold.
clear low_thresh
low_thresh is an integer from 0 and 2000000. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual total number of PDP Contexts is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual total number of PDP contexts is less than the low threshold.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a total number of PDP contexts per GPRS session high threshold count of 10000 for a system using the Alert thresholding model:
high_thresh is an integer from 0 through 4000000. A value of 0 disables the threshold.
clear low_thresh
low_thresh is an integer from 0 and 4000000. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual total number of HA sessions is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual total number of HA sessions is less than the low threshold.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a total number of HA sessions high threshold count of 10000 for a system using the Alert thresholding model:
high_thresh is an integer from 0 through 1000000. A value of 0 disables the threshold.
clear low_thresh
low_thresh is an integer from 0 through 1000000. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual total number of HNB-HNB-GW sessions on IuH interface is greater than the high threshold.
|
|
•
|
Clear condition: Actual total number of HNB-HNB-GW sessions on IuH interfaces is less than the low threshold.
|
Refer to the threshold poll total-hnbgw-hnb-sessions command to configure the polling interval and the threshold monitoring hnbgw-service command to enable thresholding for this value.
Important: To enable SNMP trap for threshold monitoring to this threshold use snmp trap enable ThreshTotalHNBGWHnbSess command in this mode.The following command configures the total number of HNB-GW-HNB sessions on IuH interfaces to a high threshold count of 10000 for a system using the Alert thresholding model:
high_thresh is an integer from 0 through 3000000. A value of 0 disables the threshold.
clear low_thresh
low_thresh is an integer from 0 through 3000000. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual total number of subscriber sessions across all HNB-GW service on a system is greater than the high threshold.
|
|
•
|
Clear condition: Actual total number of subscriber sessions across all HNB-GW service on a system is less than the low threshold.
|
Refer to the threshold poll total-hnbgw-iu-sessions command to configure the polling interval and the threshold monitoring hnbgw-service command to enable thresholding for this value.
Important: To enable SNMP trap for threshold monitoring to this threshold use snmp trap enable ThreshTotalHNBGWIuSess command in this mode.The following command configures the total number of subscriber sessions towards CN across all HNB-GW services to a high threshold count of 30000 for a system using the Alert thresholding model:
high_thresh is an integer from 0 through 4000000. A value of 0 disables the threshold.
clear low_thresh
low_thresh is an integer from 0 and 4000000. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual total number of UEs connected to HNB-GW service across all HNB-GW services on a system is greater than the high threshold.
|
|
•
|
Clear condition: Actual total number of UEs connected to HNB-GW service across all HNB-GW services on a system is less than the low threshold.
|
Refer to the threshold poll total-hnbgw-ue-sessions command to configure the polling interval and the threshold monitoring hnbgw-service command to enable thresholding for this value.
Important: To enable SNMP trap for threshold monitoring to this threshold use snmp trap enable ThreshTotalHNBGWUeSess command in this mode.The following command configures the total number of UEs connected to HNB-GW service across all HNB-GW services to a high threshold count of 40000 for a system using the Alert thresholding model:
high_thresh is an integer from 1 through 1500000. A value of 0 disables the threshold.
clear low_thresh
low_thresh is an integer from 0 and 1500000. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual total number of HSGW sessions is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual total number of HSGW sessions is less than the low threshold.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a total number of HSGW sessions high threshold count of 500000 for a system using the Alert thresholding model:
high_thresh is an integer from 1 through 1500000. A value of 0 disables the threshold.
clear low_thresh
low_thresh is an integer from 0 through 1500000. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual total number of LMA sessions is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual total number of LMA sessions is less than the low threshold.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a total number of LMA sessions high threshold count of 500000 for a system using the Alert thresholding model:
high_thresh is an integer value from 0 through 4000000. A value of 0 disables the threshold.
clear low_thresh
low_thresh is an integer from 0 and 4000000. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual total number of LNS sessions is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual total number of LNS sessions is less than the low threshold
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a total LNS session high threshold count of 10000 for a system using the Alert thresholding model:
high_thresh is an integer value from 0 through 4000000. A value of 0 disables the threshold.
clear low_thresh
low_thresh is an integer from 0 and 4000000. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual total number of MME sessions is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual total number of MME sessions is less than the low threshold
|
Refer to the threshold poll total-mme-sessions command to configure the polling interval and the threshold monitoring mme-service command to enable thresholding for this value.
The following command configures a total MME session high threshold count of 10000 for a system using the Alert thresholding model:
high_thresh is an integer from 0 through 4000000. A value of 0 disables the threshold.
clear low_thresh
low_thresh is an integer from 0 and 4000000. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual total number of PDSN sessions is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual total number of PDSN sessions is less than the low threshold.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a total PDSN session high threshold count of 10000 for a system using the Alert thresholding model:
high_thresh is an integer from 1 through 1500000. A value of 0 disables the threshold.
clear low_thresh
low_thresh is an integer from 0 through 1500000. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual total number of P-GW sessions is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual total number of P-GW sessions is less than the low threshold
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a total number of P-GW sessions high threshold count of 500000 for a system using the Alert thresholding model:
high_thresh is an integer from 1 through 1500000. A value of 0 disables the threshold.
clear low_thresh
low_thresh is an integer from 0 through 1500000. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual total number of S-GW sessions is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual total number of S-GW sessions is less than the low threshold.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a total number of S-GW sessions high threshold count of 500000 for a system using the Alert thresholding model:
high_thresh is an integer from 1 through 2000000. A value of 0 disables the threshold.
clear low_thresh
low_thresh is an integer from 0 through 2000000. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual total number of SGSN sessions is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual total number of SGSN sessions is less than the low threshold.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a total number of SGSN sessions high threshold count of 10000 for a system using the Alert thresholding model:
high_thresh is an integer from 1 through 2000000. A value of 0 disables the threshold.
clear low_thresh
low_thresh is an integer from 0 through 2000000. A value of 0 disables the threshold.
Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.|
•
|
Enter condition: Actual total number of PDP contexts is greater than or equal to the high threshold.
|
|
•
|
Clear condition: Actual total number of PDP contexts is less than the low threshold.
|
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
The following command configures a total number of PDP contexts per SGSN session high threshold count of 10000 for a system using the Alert thresholding model:
Specifies that if in a polling interval the number of TPO DNS failures experienced by the system meets or exceeds high_thresh an alert or alarm should be generated.
high_thresh is an integer from 0 through 300000.
clear low_thresh
Specifies that if, within the polling interval, the number of TPO DNS failures experienced by the system falls below low_thresh a clear alarm should be generated.
low_thresh is an integer from 0 through 300000.
Specifies that if in a polling interval the number of TPO low-compression-gain comparison results experienced by the system meets or exceeds high_thresh an alert or alarm is generated.
high_thresh is an integer from 0 through 300000.
clear low_thresh
Specifies that if, within the polling interval, the number of TPO low-compression-gain comparison results experienced by the system falls below low_thresh a clear alarm is generated.
low_thresh is an integer from 0 through 300000.
Specifies that if in a polling interval the number of TPO RTOs experienced by the system meets or exceeds high_thresh an alert or alarm should be generated.
high_thresh is an integer from 0 through 300000.
clear low_thresh
Specifies that if, within the polling interval, the number of TPO RTOs experienced by the system falls below low_thresh a clear alarm should be generated.
low_thresh is an integer from 0 through 300000.
Enables/disables the generation of a timestamp in response to each commands entered. The timestamp does not appear in any logs as it is a CLI output only. This command affects all future CLI sessions. Use the timestamps command in the Exec Mode to change the behavior for the current CLI session only.
time session_life
Defines the maximum number of minutes that a session may exist on the system undergoing a software upgrade, before it is terminated by the system. As individual user sessions reach this lifetime limit, the system terminates the individual session(s). session_life must be an integer ranging from 1 through 1440.
usage session_num
When the threshold is crossed (when the number of sessions on the packet processing card or system is less than this value), the remaining sessions on the card or system are terminated allowing the upgrade to begin. The remaining sessions on the packet processing card or system are terminated regardless of their session life. session_num must be an integer from 0 through 6000.
Important: This command is not supported on all platforms.
Important: Software Patch Upgrades are not supported in this release.The following command sets the number of minutes a session can exist to 200, and the minimum number of sessions that may exist before terminating them to 50:
url-blacklisting database { directory path path | max-versions max_versions | override file file_name }
directory path path
path must be an alphanumeric string of 1 through 255 characters.
max-versions max_versions
max_versions must be an integer from 0 through 3.
override file file_name
file_name must be in name.extension format. For example, abc.bin. And, must be an alphanumeric string of 1 through 10 characters.
